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

Add common saved replies for issue triaging #719

Open
Nilstrieb opened this issue Dec 26, 2023 · 2 comments
Open

Add common saved replies for issue triaging #719

Nilstrieb opened this issue Dec 26, 2023 · 2 comments

Comments

@Nilstrieb
Copy link
Member

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.

@Nilstrieb Nilstrieb changed the title Add common saves replies for issue triaging Add common saved replies for issue triaging Dec 26, 2023
@apiraino
Copy link
Contributor

great idea, if you intend to add them to the forge documentation (I think I would look for them there). And people can copy and save them as "saved replies" for comment templates.

@apiraino
Copy link
Contributor

IIRC template comments for pull requests are handled by the triagebot (I think here) based on the codepaths changed by the patch. I'm thinking if these kind of automessages should go there

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

No branches or pull requests

2 participants