ci: add issues and PRs to FOC project board - #11
Merged
Conversation
Adds the standard FilOzone workflow that auto-adds newly opened issues and PRs to the FOC project board (org project #14), matching the canonical version in FilOzone/github-mgmt and FilOzone/synapse-sdk. This repo previously had no such automation, so recently opened items had to be added to the board manually. Requires the FILOZZY_CI_ADD_TO_PROJECT secret to be available to this repo. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Adds a GitHub Actions workflow to automatically add newly opened issues and pull requests in this repo to the FilOzone organization project board (#14), reducing manual triage work and keeping the board up to date.
Changes:
- Introduces a new workflow that triggers on
issues: openedandpull_request_target: openedto cover fork PRs. - Uses
actions/add-to-projectpinned to a specific commit (v2.0.0) andcontinue-on-errorto avoid failing when items already exist in the project.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+7
to
+11
| # This action adds all issues and PRs to the FS project board. | ||
| # It is used to keep the project board up to date with the issues and PRs. | ||
| # It is triggered by the issue and PR events. | ||
| # It assumes a `FILOZZY_CI_ADD_TO_PROJECT` secret is set in the repo. | ||
| # This secret should have the permissions outlined in https://github.com/actions/add-to-project?tab=readme-ov-file#creating-a-pat-and-adding-it-to-your-repository |
| # It is triggered by the issue and PR events. | ||
| # It assumes a `FILOZZY_CI_ADD_TO_PROJECT` secret is set in the repo. | ||
| # This secret should have the permissions outlined in https://github.com/actions/add-to-project?tab=readme-ov-file#creating-a-pat-and-adding-it-to-your-repository | ||
| name: Add issues and PRs to FS project board |
|
|
||
| jobs: | ||
| add-to-project: | ||
| name: Add all issues and prs to project |
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
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.
What
Adds the standard FilOzone workflow that automatically adds newly opened issues and PRs to the FOC project board (org project #14).
Why
An audit of issues/PRs opened across the FilOzone org in the last two weeks found that every recent item in this repo was missing from the FOC board, because this repo had no auto-add automation. Items had to be added manually (the existing backlog has now been added by hand).
This file is the canonical version copied from FilOzone/github-mgmt, modeled on synapse-sdk#700:
issues: openedandpull_request_target: opened(the latter so fork PRs are covered)actions/add-to-projectto a specific commit hash (v2.0.0)continue-on-errorso it does not fail when an item is already on the boardPrerequisite
Requires the
FILOZZY_CI_ADD_TO_PROJECTsecret to be available to this repo (repo secret, or org secret with this repo selected). If it is not yet granted, the workflow will run but be unable to add items until the secret is provisioned.