-
Notifications
You must be signed in to change notification settings - Fork 62
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
Update auto-respond-pr.yml wording #2556
base: main
Are you sure you want to change the base?
Conversation
Don't forget to add an individual reviewer (in addition to those already added, this should create a task for them in Asana). |
Generated file outputs:Time updated: Wed, 18 Dec 2024 10:25:33 GMT legacytrackers-unprotected-temporary.txt (14 more)
latestv4/android-config.json (13 more)
|
@@ -21,7 +21,7 @@ jobs: | |||
with: | |||
issue-number: ${{ github.event.pull_request.number }} | |||
body: | | |||
Don't forget to assign an individual reviewer (in addition to those already added, this should create a task for them in Asana). | |||
Don't forget to add an individual reviewer (in addition to those already added, this should create a task for them in Asana). |
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.
Maybe we can bold the reviewer part? :)
Asana Task/Github Issue:
Description
I'm seeing folk 'assign' me instead of use the reviewers field. The automation only works on the latter.
Feature change process:
Additional info:
Site breakage mitigation process:
Brief explanation
Reported URL:
Problems experienced:
Platforms affected:
Tracker(s) being unblocked:
Feature being disabled:
I have referenced the URL of this PR as the "reason" value for the exception (where applicable).
This change is a speculative mitigation to fix reported breakage.
Reference