ci: add new issues and PRs to the Vstorm OSS project - #139
Merged
Conversation
The org-wide board at projects/12 spans all six public repos. GitHub's built-in auto-add is per-repository and plan-capped, so it cannot cover them; this action can and is version-controlled with the rest of CI. The job skips with a notice while ADD_TO_PROJECT_PAT is unset rather than failing, so merging it cannot put a red cross on a stranger's first issue. It starts working by itself once the secret exists.
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Puts every new issue and pull request on the org-wide board so nothing lands in a
repo nobody is watching that week:
Vstorm OSS
Why an action rather than the project's own automation
GitHub's built-in Auto-add to project workflow is configured per repository,
and how many a project may have is capped by the org plan. Six repos do not fit.
actions/add-to-projectdoes, is version-controlled, and is the same in every repo.It is inert until a token exists
The job checks for
ADD_TO_PROJECT_PATand skips with a notice when it is absent,rather than failing. These are public repositories — a red cross on every issue a
stranger opens is a worse first impression than a board that is briefly incomplete.
It starts working on its own the moment the secret is added; nothing to merge twice.
Setup, once at the organization: a PAT with the
projectscope, stored as theorg secret
ADD_TO_PROJECT_PATand shared with these repos. The workflow's ownGITHUB_TOKENcannot be used — it has no access to organization projects.Notes for review
pull_request_targetis deliberate and the file explains why: fork PRs get nosecrets under
pull_request, and this job never checks out contributor code —no checkout, no build, no script from the PR. If that ever changes, so must the trigger.
permissions: {}— nothing writes throughGITHUB_TOKEN.vars.DISABLE_ADD_TO_PROJECTturns it off per repo without a revert.