| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks! — will it re-run if we re-open a PR? Just wondering what the merge flow looks like for core devs
Sorry, something went wrong.
|
Looks good! |
Sorry, something went wrong.
| pull-requests: write | ||
|
|
||
| on: | ||
| pull_request: |
There was a problem hiding this comment.
This should let a core dev reopen an auto-closed PR if need be:
GitHub's documentation states:
By default, a workflow only runs when a pull_request event's activity type is opened, synchronize, or reopened.
I haven't tested it, but it seems by default we'd have an auto-close loop.
| pull_request: | |
| pull_request: | |
| types: | |
| - opened |
Sorry, something went wrong.
|
We do not accept PRs on this repository. Please file an issue at https://github.com/python/cpython requesting an update to the binary packages in this repository. |
Sorry, something went wrong.
No, it stayed open after re-open (and was later closed by the hourly cron). |
Sorry, something went wrong.
|
I'll re-open and merge this :) |
Sorry, something went wrong.
|
We do not accept PRs on this repository. Please file an issue at https://github.com/python/cpython requesting an update to the binary packages in this repository. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Re: #5 (comment)
The cron was disabled four months ago:
This triggers the autoclose when opening a PR.
For a demo, see:
(This PR will be autoclosed the next time the schedule runs, we'll just have to re-open it before merge 😅)