-
Notifications
You must be signed in to change notification settings - Fork 80
Remove label subscriptions #3066
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
Remove label subscriptions #3066
Conversation
0d4a8d5 to
4fbf507
Compare
josephsnyder
left a comment
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.
One requested update about a link to nowhere, but also a further question: is this page just fundamentally broken?
I don't see the save button appear when edits are made to the selections or even some of the headers like the hidden Email me: element which makes the selections starting with when ... actually make sense. They all appear to be hidden by a if test="/cdash/edit=1"
4fbf507 to
8570600
Compare
|
@josephsnyder I had the same thought at first--it took me a while to realize that you need to add |
josephsnyder
left a comment
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 the answer and the update. LGTM!
Following the discussion in #3066 (review), this PR removes the unnecessary `edit` query parameter from the project notifications page. A PR which completely overhauls this page is planned for the future, but this temporary improvement is good enough for now.
CDash historically offered the ability to subscribe to notifications on a per-label basis, meaning that users could subscribe to the portion of the errors relevant to them without being bothered by errors related to other parts of the codebase. This functionality is currently broken, causes performance issues for several fundamental reasons, and is entirely untested. This PR removes the feature entirely. If a similar feature is desired in the future, we can re-evaluate it as a new feature designed and written from the ground up.