mirror of
https://github.com/hl-archive-node/nanoreth.git
synced 2025-12-06 10:59:55 +00:00
s/foundry-rs/paradigmxyz
This commit is contained in:
@ -5,7 +5,7 @@ Each label in the repository has a description attached that describes what the
|
||||
There are 7 label categories in the repository:
|
||||
|
||||
- **Area labels**: These labels denote the general area of the project an issue or PR affects. These start with [`A-`][area].
|
||||
- **Category labels**: These labels denote the type of issue or change being made, for example https://github.com/foundry-rs/reth/labels/C-bug or https://github.com/foundry-rs/reth/labels/C-enhancement. These start with [`C-`][category].
|
||||
- **Category labels**: These labels denote the type of issue or change being made, for example https://github.com/paradigmxyz/reth/labels/C-bug or https://github.com/paradigmxyz/reth/labels/C-enhancement. These start with [`C-`][category].
|
||||
- **Difficulty labels**: These are reserved for the very easy or very hard issues. Any issue without one of these labels can be considered to be of "average difficulty". They start with [`D-`][difficulty].
|
||||
- **Meta labels**: These start with [`M-`][meta] and convey meaning to the core contributors, usually about the release process.
|
||||
- **Platform labels**: These describe the platform an issue is present on. They start with [`O-`][platform].
|
||||
@ -18,26 +18,26 @@ For easier at-a-glance communication of the status of issues and PRs the followi
|
||||
|
||||
**Needs work**
|
||||
|
||||
- https://github.com/foundry-rs/reth/labels/S-blocked
|
||||
- https://github.com/foundry-rs/reth/labels/S-needs-benchmark
|
||||
- https://github.com/foundry-rs/reth/labels/S-needs-design
|
||||
- https://github.com/foundry-rs/reth/labels/S-needs-investigation
|
||||
- https://github.com/foundry-rs/reth/labels/S-needs-rebase
|
||||
- https://github.com/paradigmxyz/reth/labels/S-blocked
|
||||
- https://github.com/paradigmxyz/reth/labels/S-needs-benchmark
|
||||
- https://github.com/paradigmxyz/reth/labels/S-needs-design
|
||||
- https://github.com/paradigmxyz/reth/labels/S-needs-investigation
|
||||
- https://github.com/paradigmxyz/reth/labels/S-needs-rebase
|
||||
|
||||
**Closure reasons**
|
||||
|
||||
- https://github.com/foundry-rs/reth/labels/S-duplicate
|
||||
- https://github.com/foundry-rs/reth/labels/S-wontfix
|
||||
- https://github.com/paradigmxyz/reth/labels/S-duplicate
|
||||
- https://github.com/paradigmxyz/reth/labels/S-wontfix
|
||||
|
||||
**Misc.**
|
||||
|
||||
- https://github.com/foundry-rs/reth/labels/S-needs-triage
|
||||
- https://github.com/foundry-rs/reth/labels/S-controversial
|
||||
- https://github.com/paradigmxyz/reth/labels/S-needs-triage
|
||||
- https://github.com/paradigmxyz/reth/labels/S-controversial
|
||||
|
||||
[area]: https://github.com/foundry-rs/reth/labels?q=a-
|
||||
[category]: https://github.com/foundry-rs/reth/labels?q=c-
|
||||
[difficulty]: https://github.com/foundry-rs/reth/labels?q=d-
|
||||
[meta]: https://github.com/foundry-rs/reth/labels?q=m-
|
||||
[platform]: https://github.com/foundry-rs/reth/labels?q=o-
|
||||
[priority]: https://github.com/foundry-rs/reth/labels?q=p-
|
||||
[status]: https://github.com/foundry-rs/reth/labels?q=s-
|
||||
[area]: https://github.com/paradigmxyz/reth/labels?q=a-
|
||||
[category]: https://github.com/paradigmxyz/reth/labels?q=c-
|
||||
[difficulty]: https://github.com/paradigmxyz/reth/labels?q=d-
|
||||
[meta]: https://github.com/paradigmxyz/reth/labels?q=m-
|
||||
[platform]: https://github.com/paradigmxyz/reth/labels?q=o-
|
||||
[priority]: https://github.com/paradigmxyz/reth/labels?q=p-
|
||||
[status]: https://github.com/paradigmxyz/reth/labels?q=s-
|
||||
@ -2,7 +2,7 @@
|
||||
|
||||
1. Update the version in `Cargo.toml`
|
||||
2. Update the changelog[^1]
|
||||
- Check that all issues marked https://github.com/foundry-rs/reth/labels/M-changelog have been added to the changelog
|
||||
- Check that all issues marked https://github.com/paradigmxyz/reth/labels/M-changelog have been added to the changelog
|
||||
- Move the "Unreleased" section in the changelog under a new header with the new version, and fix up the links in the bottom of the file
|
||||
3. Ensure tests and lints pass
|
||||
4. Commit the new changelog and version bump
|
||||
|
||||
Reference in New Issue
Block a user