Skip to content

Conversation

@ryan953
Copy link
Member

@ryan953 ryan953 commented Nov 7, 2025

Before the job wasnt running properly because env.SECRET_ACCESS was some copy+pasta that doesnt work in this workflow. Instead the fix is to stop the job on failure, and have fewer conditions on each step

Before the job wasnt running properly because `env.SECRET_ACCESS` was some copy+pasta that doesnt work in this workflow. Instead the fix is to stop the job on failure, and have fewer conditions on each step
@ryan953 ryan953 requested a review from a team as a code owner November 7, 2025 03:22
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Nov 7, 2025
- # get a non-default github token so that any changes are verified by CI
if: env.SECRET_ACCESS == 'true'
uses: getsentry/action-github-app-token@d4b5da6c5e37703f8c3b3e43abb5705b46e159cc # v3.0.0
- uses: getsentry/action-github-app-token@d4b5da6c5e37703f8c3b3e43abb5705b46e159cc # v3.0.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Token Step Fails Job; Continue-On-Error Missing

The action-github-app-token step lacks continue-on-error: true, causing the entire job to fail if token generation fails. This prevents python3 -m tools.api_urls_to_typescript from running, unlike similar jobs (requirements, typing) which use continue-on-error: true to ensure the main task executes regardless of token availability.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants