Skip to content

Add a workflow to add issues/PRs to projects. #94447

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Jul 1, 2022
Merged

Add a workflow to add issues/PRs to projects. #94447

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
22aff1b
Add a workflow to add issues/PRs to projects.
ezio-melotti Jun 30, 2022
fee99be
Apply suggestions from code review
ezio-melotti Jun 30, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions .github/workflows/project-updater.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
name: Update projects when an issue/PR is created/labeled
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This name shows in the left bar at https://github.com/python/cpython/actions, can we make it a bit shorter?

image

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We want something about "projects" being "updated", and possibly "GitHub projects" or "(beta) projects" since "projects" is a bit generic. Mentioning "labels" would also be good, since they are the trigger of the action.

Is "Update GH projects on label change" good? The last word might not fit, but it's not essential. Otherwise I can just drop the "GH" and it should fit.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO, "GH" is more important to keep than "change", since otherwise I think it would be confusing and unclear what projects were being referred to, whereas change just clarifies the exact trigger but as you say, is not essential to understanding meaning


on:
issues:
types:
- opened
- labeled
pull_request:
types:
- opened
- labeled

jobs:
add-to-project:
name: Add to the Release and Deferred blocker project
runs-on: ubuntu-latest
steps:
- uses: actions/[email protected]
with:
project-url: https://github.com/orgs/python/projects/2
github-token: ${{ secrets.ADD_TO_PROJECT_PAT }}
labeled: release-blocker, deferred-blocker
label-operator: OR