-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
chore: move tip about prioritizing issues #18071
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for opening this PR! We do want this text to appear in the issue though, so that users who find the issue are encouraged to react to it if they want to see it being worked on. I believe, moving this to be non-editable in the issue creation form (via attributes), doesn't actually make it visibile in the issue, correct?
ohhh. I never noticed... you are right 😮 |
|
@Lms24 I experimented with it and I think I have found a solution that works. If not, feel free to close the PR. 👍🏽 |
|
Created Issue: OrbisK#4 Form: https://github.com/OrbisK/sentry-javascript-fork/issues/new?template=bug.yml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks -- nice workaround! One more small change but I'll merge this in a sec
Updated the tip for prioritizing features in the issue template.
Updated the tip message to remove redundant text.
|
realizing I never merged this because auto-merge was blocked on a formatting issue. Should be fixed now. Sorry for the delay and thanks again for contributing! |
I think this tip should apply to every bug or feature issue that is reported.
There is no need for it to be editable from the text area.
PREVIEW