|
Ran
|
Jobs
1
|
Files
95
|
Run time
1min
|
Badge
README BADGES
|
push
github
Merge rust-bitcoin/rust-bitcoin#3081: githooks: Added post-merge githook to check if hooks changed <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/a7fa237d321257d56ce4fa674b53edd03e9ec4d8">a7fa237d3 githooks: Added post-merge githook to check if hooks changed (Ryan Breen) Pull request description: Referring back to [this post](https://github.com/rust-bitcoin/rust-bitcoin/pull/2980#discussion_r1673140172) in #2980, there was discussion that a post-merge githook should be added to check if the user's copied githooks have changed. In order to distinguish between a githook that a user installed themselves and a rust-bitcoin githook, I chose to add a tag at the beginning of the project's hooks. ACKs for top commit: Kixunil: ACK a7fa237d321257d56ce4fa674b53edd03e9ec4d8 apoelstra: ACK a7fa237d321257d56ce4fa674b53edd03e9ec4d8 I have never used `git pull` but I also have not ever used githooks, so I guess this is good Tree-SHA512: 90314fea8b2ecd015c7a1cc77005098237c
19670 of 23630 relevant lines covered (83.24%)
15590.1 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 10124892552.1 | 0 |
83.24 |
GitHub Action Run |