-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Improve "rustdoc.md" issue template #145143
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
base: master
Are you sure you want to change the base?
Conversation
I can't tell how the changed wording is actually different from the existing wording? I don't really have strong opinions on this. |
The text change here doesn't seem like an improvement, and I'm not sure what connection it has to the description of this PR. "bug reports or feature requests, which may be confused with feature requests"? I don't think this change should be merged in its current form. |
https://rust-lang.zulipchat.com/#narrow/channel/242269-t-release.2Ftriage/topic/Issue.20templates
"Feature request" is included in the descriptions of these two places. This may make people who open it for the first time a little confused. So simply say "Create a report for a change to |
So, reading the discussion on Zulip I think there is perhaps a suggestion (see comment) that could be an improvement
We should be careful and deliberate with changes like these because these templates are at the frontline of our issue tracker 🙂 @rustbot author |
Signed-off-by: xizheyin <[email protected]>
c516d8e
to
be478d1
Compare
diagnostic.yaml
to reduce confusion
I understand, thank you. :)
#145130 has done it.
I rename it to @rustbot ready |
I rename the title of
rustdoc.md
toProblem with rustdoc tool
, which is clearer.