feat: prefer unique e2e ci repo rather than branch#573
Open
drbh wants to merge 1 commit into
Open
Conversation
danieldk
approved these changes
May 20, 2026
Member
danieldk
left a comment
danieldk
left a comment
There was a problem hiding this comment.
Nice! Seems to have surfaced an issue.
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
3 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.
This PR restructures the e2e workflow to write to a unique repo id per run id and run attempt rather than a fixed repo id. This has the benefit of avoiding conflicts of writing to the same repo, and removes the need to add a concurrency group to handle possible race condition. These changes ensure that a each ci job will create a new repo and push, test it works, then clean up the repo at the end of the workflow.