Prevent "Move labelled issues to correct projects" GitHub Actions workflow from failing when an issue is already on the project board#18755
Merged
anoadragon453 merged 2 commits intodevelopfrom Aug 5, 2025
Conversation
reivilibre
approved these changes
Aug 4, 2025
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.
The "Move labelled issues to correct projects" exists to move issues to the "Needs info" column on our internal triage queue GitHub project board when the
X-Needs-Infolabel is added to it.The workflow will currently fail if the issue is already on the project board (which is most of the time).
This change will prevent the workflow from failing in this case - instead carrying on even if the "actions/add-to-project" step failed.
Ideally there would be a "no-op option" on the "add-to-project" action so we didn't have to ignore any other failures as well, but alas, there is not. Still, if the issue failed to be added to the project, then the subsequent step will fail anyways (as the issue is not on the project).
Pull Request Checklist
EventStoretoEventWorkerStore.".code blocks.