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
To enable the use of https://github.blog/changelog/2022-08-23-new-options-for-controlling-the-default-commit-message-when-merging-a-pull-request/ so we can have good defaults for commit messages, we need to ensure that PR descriptions don't contain @ tags of GitHub users. We can lint for this but the auto-cc bot edits PR descriptions to @ people on PRs, so we need to change this bot to leave a comment instead. Right now we have other bots that leave comments on PRs, this would be a good time to refactor them a bit and merge everything into 1 big bot comment. This could also contain helpful links for contributors and let us get rid of the pr template.
To implement the lint check there are a few sequential PRs:
areusch
added
the
needs-triage
PRs or issues that need to be investigated by maintainers to find the right assignees to address it
label
Oct 19, 2022
janetsc
added
dev:ci
and removed
needs-triage
PRs or issues that need to be investigated by maintainers to find the right assignees to address it
labels
Oct 19, 2022
To enable the use of https://github.blog/changelog/2022-08-23-new-options-for-controlling-the-default-commit-message-when-merging-a-pull-request/ so we can have good defaults for commit messages, we need to ensure that PR descriptions don't contain @ tags of GitHub users. We can lint for this but the auto-cc bot edits PR descriptions to @ people on PRs, so we need to change this bot to leave a comment instead. Right now we have other bots that leave comments on PRs, this would be a good time to refactor them a bit and merge everything into 1 big bot comment. This could also contain helpful links for contributors and let us get rid of the pr template.
To implement the lint check there are a few sequential PRs:
Then to implement the unified bot comment on PRs:
cc @Mousius @areusch @gigiblender @gromero
The text was updated successfully, but these errors were encountered: