You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the enhancement or feature you would like
This is something I find myself informing new contributors about daily. It should be made more visible in some way. (Then there is the problem of increasing the viability of the devguide itself...)
For now I think it would be good to move the section to just below the submitting section rather than the bottom of the file.
Describe alternatives you have considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
StanFromIreland
changed the title
Feature: Enhance the visibility of the "Update branch button"
Feature: Enhance the visibility of the "Update branch button" section
Mar 4, 2025
I'm not clear on why this needs to move, or why it's being pointed out daily. The last point of the section is very relevant:
Do not click Update branch without a good reason because it notifies everyone watching the PR that there are new changes, when there are not, and it uses up limited CI resources.
In many cases, it's probably best that it not be used except by someone merging the PR.
I wonder if a better solution might be for @bedevere-bot to watch for the merge commits created by the button, and complain if they look abusive (more than one in a row, more than one in a day, multiple without a diff, etc.).
Describe the enhancement or feature you would like
This is something I find myself informing new contributors about daily. It should be made more visible in some way. (Then there is the problem of increasing the viability of the devguide itself...)
For now I think it would be good to move the section to just below the submitting section rather than the bottom of the file.
Describe alternatives you have considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: