|
Ran
|
Jobs
1
|
Files
99
|
Run time
1min
|
Badge
README BADGES
|
push
github
Merge rust-bitcoin/rust-bitcoin#3439: sequence: clarify sequence constant name and add FINAL <a class=hub.com/rust-bitcoin/rust-bitcoin/commit/<a class="double-link" href="https://git"><a class=hub.com/rust-bitcoin/rust-bitcoin/commit/4499b5c95b19fdbb895bd57ee709697a9b6c8762">4499b5c95<a href="https://github.com/rust-bitcoin/rust-bitcoin/commit/0a83e5336d9f88e5f1f9a31b110c5ef5bae3714f"> feat: rename ENABLE_RBF_NO_LOCKTIME to ENABLE_LOCKTIME_AND_RBF (ChrisCho-H) <a class="double-link" href="https://github.com/rust-bitcoin/rust-bitcoin/commit/861d97de368c6cdb53dbd95373df2e88596685df">861d97de3</a><a href="https://github.com/rust-bitcoin/rust-bitcoin/commit/0a83e5336d9f88e5f1f9a31b110c5ef5bae3714f"> feat: add FINAL constant to disable all (ChrisCho-H) Pull request description: </a><a class="double-link" href="https://github.com/rust-bitcoin/rust-bitcoin/commit/c24630e7b13312ea34f0f54ed832783ced8dde3f">c24630e7b</a><a href="https://github.com/rust-bitcoin/rust-bitcoin/commit/0a83e5336d9f88e5f1f9a31b110c5ef5bae3714f"> - `LOCKTIME` is used for both absolute and relative one without clear classification, which is confusing and could lead to an unexpected bug. Although it's API breaking change, current constant is so ambiguous unless understand the details of `LOCKTIME` semantic. 9cc5dfeef - Add constant `ENABLE_ALL` and `DISABLE_ALL`, which is useful for those who want to enable(disable) rbf, absolute/relative locktime. ACKs for top commit: tcharding: ACK 4499b5c95b19fdbb895bd57ee709697a9b6c8762 apoelstra: ACK 4499b5c95b19fdbb895bd57ee709697a9b6c8762 successfully ran local tests Tree-SHA512: dbea5ae914f696920970de42d8fe88ce8fc
19095 of 23113 relevant lines covered (82.62%)
18859.67 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 11227625500.1 | 0 |
82.62 |
GitHub Action Run |