add initial action for issue label -> project status sync #8591
Conversation
This file contains 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
alexrashed
added
the
semver: minor
thrau
approved these changes
Jun 29, 2023
alexrashed
force-pushed
the
add-project-sync
branch
from
f200018
to
15aa2dd
Compare
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.
We are currently testing a private GitHub Project (Beta / V2) to organize the issues in this repo.
Unfortunately, the new projects do not provide a sync (not even unidirectional) between labels and GitHub Project fields (like the status).
This PR adds a small action which acts on issue (un-)label events to set a specific status value on a project card based on the labels set.
This is only a prototypical and uni-directional sync, issue labels -> project card status. The other way around (project card status -> issue labels) is unfortunately also not solvable with GitHub actions, because org projects do not trigger issue events. This could be solved if we decide to move the board from the org to the repo.
I'm grateful for any feedback!