-
Notifications
You must be signed in to change notification settings - Fork 113
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
color prs purple #264
Comments
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made. |
ping |
Hopefully we can get this working with the new commit-queue |
If the bot can make modifications to the head branch, force push to the head branch so it lands with the purple icon on GitHub instead of the red icon when the PR is closed. Let's gooooooooo! Ref: nodejs/node-core-utils#264
If the bot can make modifications to the head branch, force push to the head branch so it lands with the purple icon on GitHub instead of the red icon when the PR is closed. Let's gooooooooo! Ref: nodejs/node-core-utils#264
If the bot can make modifications to the head branch, force push to the head branch so it lands with the purple icon on GitHub instead of the red icon when the PR is closed. Let's gooooooooo! Ref: nodejs/node-core-utils#264
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made. |
bump |
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made. |
bump forever |
I think we can close this, the CQ is able to purple merge PRs that land one commit, the current workflow seems to be an appropriate compromise. |
from the collab guide:
The text was updated successfully, but these errors were encountered: