I tested that the issue is added to the project when:
the release-blocker label is applied
the deferred-blocker label is applied
removing the label doesn't remove the issue from the project
there doesn't seem to be a way to set the type automatically from the action
it can be set manually either in the issue or in the project
it takes about 10-15s before the issue (dis)appears in the project
a manual refresh on the issue is needed before the project (dis)appears in the sidebar
After attempting backports in python/cpython#94477 and python/cpython#94475, the check failed because it couldn't access the secret. After some investigation it turns out that PRs created from forks can't access secrets. In addition, this action would add a check for each job in the PR (currently only one, but I'm planning to add more for the other labels/projects):
Click to see screenshot of the job in the PR checks list
Therefore, I submitted python/cpython#94483 to remove the pull_request trigger and only run the action for issues, solving the issue with the secret and the extra checks in PRs.
The text was updated successfully, but these errors were encountered:
ezio-melotti commentedJul 1, 2022
•
edited
This is a meta issue about a newly added GitHub action that automatically updates projects:
pull_requesttrigger from the project-updater GHA. cpython#94483sprintissues to the Sprint 2022 project. cpython#97788python/cpython#94447 added a first version of the workflow that updates the Release and Deferred blockers project, and:
release-blockerlabel is applieddeferred-blockerlabel is appliedAfter attempting backports in python/cpython#94477 and python/cpython#94475, the check failed because it couldn't access the secret. After some investigation it turns out that PRs created from forks can't access secrets. In addition, this action would add a check for each job in the PR (currently only one, but I'm planning to add more for the other labels/projects):
Click to see screenshot of the job in the PR checks list
Therefore, I submitted python/cpython#94483 to remove the
pull_requesttrigger and only run the action for issues, solving the issue with the secret and the extra checks in PRs.The text was updated successfully, but these errors were encountered: