Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase the stale interval (or threshold) from 30 to 180 days since last activity in PR (RFC book) #134

Closed
anaelleltd opened this issue Dec 16, 2024 · 1 comment · Fixed by paritytech/RFCs#4

Comments

@anaelleltd
Copy link
Contributor

anaelleltd commented Dec 16, 2024

Some of the info displayed in the RFC book is inaccurate.
For example, there are a lot of PRs that have been filed in the "stale" category, though they are less than 3 months old.
Also, draft PRs are tagged as "stale", even though they are ongoing.

@paritytech/opstooling

@anaelleltd
Copy link
Contributor Author

anaelleltd commented Dec 16, 2024

Specifically, the following RFCs should not be in the Stale category:
image

Edit: It would be good to increase the stale interval (or threshold) from 30 to 180 days since last activity in PR. This would re-render the mdbook and re-group the RFCs accordingly to the new rule.

Thanks!

@anaelleltd anaelleltd changed the title Errors in RFC book Increase the stale interval (or threshold) from 30 to 180 days since last activity in PR (RFC book) Dec 16, 2024
mordamax added a commit to paritytech/RFCs that referenced this issue Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant