rust-bitcoin / rust-bitcoin / 8366578065

83%

push

github

Merge rust-bitcoin/rust-bitcoin#2617: Revert #2525 (filter CI)

<a class=hub.com/rust-bitcoin/rust-bitcoin/commit/50e772fe7921f3b73858f857aa049839a118122c">50e772fe7<a href="https://github.com/rust-bitcoin/rust-bitcoin/commit/2b9568158b22429488e0240836eba9cc33662823"> Revert &quot;ci: introduce `classify-pr.sh` script which determines whether a PR should have CI run" (Andrew Poelstra)
<a class="double-link" href="https://github.com/rust-bitcoin/rust-bitcoin/commit/ae381fcc0191d4218766a82458892ff2faa793ed">ae381fcc0</a><a href="https://github.com/rust-bitcoin/rust-bitcoin/commit/2b9568158b22429488e0240836eba9cc33662823"> Revert &quot;ci: gate CI workflow on source being changed&quot; (Andrew Poelstra)
</a><a class="double-link" href="https://github.com/rust-bitcoin/rust-bitcoin/commit/495d7e8acd27adf8277e554067536d2021a69995">495d7e8ac</a><a href="https://github.com/rust-bitcoin/rust-bitcoin/commit/2b9568158b22429488e0240836eba9cc33662823"> Revert &quot;ci: gate fuzztesting on whether source code changed" (Andrew Poelstra)
ec3e4e880 Revert "ci: gate coverage analysis on whether source code changed" (Andrew Poelstra)

Pull request description:

  This PR did not work on the "master" CI runs and I really don't care enough to figure it out (or even how to test it). Just revert it.

ACKs for top commit:
  tcharding:
    ACK 50e772fe7921f3b73858f857aa049839a118122c

Tree-SHA512: c56b77dab2985229610e629bc797e1cc997

19873 of 23683 relevant lines covered (83.91%)

16345.55 hits per line