fix: remove GitHub org/repo in error messages#3808
Merged
Conversation
erika-wallace
temporarily deployed
to
AcceptanceTests
GitHub Actions
Inactive
erika-wallace
temporarily deployed
to
AcceptanceTests
GitHub Actions
Inactive
erika-wallace
temporarily deployed
to
AcceptanceTests
GitHub Actions
Inactive
erika-wallace
temporarily deployed
to
AcceptanceTests
GitHub Actions
Inactive
jdodson
approved these changes
Jul 10, 2026
jdodson
left a comment
jdodson
left a comment
Contributor
There was a problem hiding this comment.
Looks good!
What I did:
- Eyeballed the changes. Not a lot, looks good.
- Ran through a light code review process with Claude, that also looks good.
- Hand tested it as you noted and that also confirmed the fix too.
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.
Summary
This PR updates
getRepo()error handling to avoid exposing GitHub org/repo names in thrown error messages. Also, it preserves HTTP status codes on the new error so existing telemetry filters treat 4xx as user errors.Type of Change
Breaking Changes (major semver update)
!after your change type to denote a change that breaks current behaviorFeature Additions (minor semver update)
Patch Updates (patch semver update)
Testing
Notes:
Requires a Heroku pipeline for testing.
Steps:
npm i && npm run build./bin/run pipelines:connect PIPELINE -r fake-repo/xyz- should not contain Github org/repo nameScreenshots (if applicable)
Related Issues
GUS work item: W-20503496