fix: handle 404 gracefully when a governance team does not exist#20
Merged
Conversation
bfabio
reviewed
Jun 11, 2026
The applied suggestion changed only the source. The action runs the committed bundle, which still logged at warn level.
Contributor
|
Thanks @lsmith77! |
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.
The bot crashes with an unhandled RequestError (404) when calling listMembersInOrg for a team that doesn't exist in the org. This causes every comment on every issue to trigger a failing action run.
The fix follows the same pattern already used in removeLabel in the same file: catch the 404, log a warning, and return false (not a member) instead of throwing. Any other error is still re-thrown. The RequestError type needed for the cast is already imported.
Fixes the failure visible in https://github.com/publiccodeyml/publiccode.yml/acti