diff options
| author | merge-script <fanquake@gmail.com> | 2024-09-05 14:53:48 +0100 |
|---|---|---|
| committer | merge-script <fanquake@gmail.com> | 2024-09-05 14:53:48 +0100 |
| commit | d661e2b1b771abafb0b152842d775d3150032230 (patch) | |
| tree | a465948dae913b3bc22e599e86b3546ad9cb1a9a /src/node | |
| parent | d6a1b94ffdd845cd4886fd468f0e5910740eaf1d (diff) | |
| parent | fa3a7ebe5b5db63e4cb4fb6974c028cc7af0b898 (diff) | |
| download | bitcoin-d661e2b1b771abafb0b152842d775d3150032230.tar.xz | |
Merge bitcoin/bitcoin#30812: lint: Check for release note snippets in the wrong folder
fa3a7ebe5b5db63e4cb4fb6974c028cc7af0b898 lint: Check for release note snippets in the wrong folder (MarcoFalke)
Pull request description:
It is a common mistake to place the snippets in the wrong folder, where they could be missed. For example https://github.com/bitcoin/bitcoin/pull/30719#pullrequestreview-2262535007 or commit 84900ac34f6888b7a851d0a6a5885192155f865c.
Fix all issues by adding a simple lint check.
Can be tested by reverting a prior commit that violated the rule and then running the new check:
```
git revert 35ef34eab7b36e3c53ed438d74a9b783cbcaec27
( cd ./test/lint/test_runner/ && RUST_BACKTRACE=1 cargo run -- --lint=doc_release_note_snippets )
ACKs for top commit:
l0rinc:
ACK fa3a7ebe5b5db63e4cb4fb6974c028cc7af0b898
TheCharlatan:
Re-ACK fa3a7ebe5b5db63e4cb4fb6974c028cc7af0b898
Tree-SHA512: 65a13696178aa8f94daa12a767cc74861293c631c19da9ca23c0fd43cedd47e7928d0ef14ad9ad83a434c1ac0e006f5a632ba9679756e071dea65b3cbf927c2d
Diffstat (limited to 'src/node')
0 files changed, 0 insertions, 0 deletions