rust-lang / rust-lang/rust-forge
Add common saved replies for issue triaging
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 568
- Forks
- 253
- Avg merge
- 5h 33m
- Merged PRs (30d)
- 12
Description
I've recently started to write saved replies for triaging. It would be nice to share them here so people can use the same replies. We can also iterate on them together to ensure high quality.
For example, what I've created:
Closing this issue as unactionable. If you can provide a reproduction, we can re-open the issue, but without one, there is nothing we can do.
Thank you for the report! It would be useful to bisect the regression using cargo-bisect-rustc to make it easier to figure out what happened and ping the relevant people
Thank you for the PR! This PR contains a public library API change, which should follow the proper process: https://std-dev-guide.rust-lang.org/development/feature-lifecycle.html
The last one isn't about issues but is still useful.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is identified. Start by locating where shared issue-triage guidance or saved replies belong in the repository, then confirm the intended location and reply set with maintainers. Done means the agreed common replies are documented and available for triaging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100