DT-3284: Fix GitHub App authentication flow in dispatch workflows #326
Conversation
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
- Generate GitHub App token as first step in dispatch workflows - Use token for checkout with fetch-depth: 0 - Configure Git and gh CLI auth after checkout - Simplify commit-changes action to only handle commits - Follows pattern from temporal-worker-controller release workflow This ensures the GitHub App token is used throughout the entire workflow, addressing repository rule violations for push operations. Jira: DT-3284
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.
Summary
Moves GitHub App authentication setup to the workflows themselves to ensure proper token usage throughout the entire workflow.
Problem
Push operations were failing with: "Required workflow 'Check for CODEOWNERS' is not satisfied"
The issue was that we need the GitHub App token from the very beginning of the workflow, including for the checkout step.
Solution
Following the pattern from temporal-worker-controller release workflow:
Testing
The changes will be validated when the next dispatch workflow runs after merging.
Jira
DT-3284