Skip to content

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.

Sign up for GitHub

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

Jump to bottom
Merged
Lms24 merged 13 commits into from
Nov 17, 2025
Merged

chore: move tip about prioritizing issues #18071

Lms24 merged 13 commits into from
Nov 17, 2025

Conversation

@OrbisK
Copy link
Contributor

@OrbisK OrbisK commented Oct 31, 2025 •
edited
Loading

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
cursor[bot]

This comment was marked as outdated.

Sign in to view

Lms24
Lms24 reviewed Oct 31, 2025
View reviewed changes
Copy link
Member

@Lms24 Lms24 left a comment •
edited
Loading

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?
@OrbisK
Copy link
Contributor Author

OrbisK commented Oct 31, 2025

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 😮
@OrbisK OrbisK marked this pull request as draft October 31, 2025 16:12
@OrbisK OrbisK marked this pull request as ready for review October 31, 2025 16:30
@OrbisK
Copy link
Contributor Author

OrbisK commented Oct 31, 2025

@Lms24 I experimented with it and I think I have found a solution that works. If not, feel free to close the PR. 👍🏽
@OrbisK
Copy link
Contributor Author

OrbisK commented Oct 31, 2025

Created Issue: OrbisK#4

Form: https://github.com/OrbisK/sentry-javascript-fork/issues/new?template=bug.yml
Lms24
Lms24 reviewed Nov 3, 2025
View reviewed changes
Copy link
Member

@Lms24 Lms24 left a comment •
edited
Loading

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
@Lms24 Lms24 enabled auto-merge (squash) November 3, 2025 08:45
@Lms24
Copy link
Member

Lms24 commented Nov 17, 2025

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!
@Lms24 Lms24 merged commit 4ad4d92 into getsentry:develop Nov 17, 2025
58 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants

@OrbisK @Lms24