feat: Demarcate bot raised PRs #36
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
On the assumption that PRs raised by a human should be prioritised, add a prefix to bot raised PRs to provide a visual difference between the two. Also add the PR author to the message.
akash1810
force-pushed
the
aa/add-username
branch
from
fffd9dd
to
b238eb2
Compare
emdash-ie
approved these changes
Oct 23, 2024
NovemberTang
approved these changes
Oct 23, 2024
AshCorr
approved these changes
Oct 23, 2024
akash1810
added a commit
that referenced
this pull request
Oct 23, 2024
Following on from #36, this change keeps the message structure more uniform. This should mean the messages are slightly easier to visually parse.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this change?
On the assumption that PRs raised by a human should be prioritised, add a prefix to bot raised PRs to provide a visual difference between the two. Also add the PR author to the message.
Alternative solution
An alternative to this would be to group bot PRs together. This would then allow a summary to be provided too, for example:
However, this would require more of a refactor.
How to test
Follow the instructions in the README to run locally.
How can we measure success?
PRs raised from colleagues are triaged faster. NOTE: I've not got any metrics to suggest this is actually a problem, just anecdotal experience.
Have we considered potential risks?
Are the messages too noisy?
Images
Before
After