Skip to content

Conversation

@Chickensoupwithrice
Copy link
Contributor

@Chickensoupwithrice Chickensoupwithrice commented Jun 25, 2025

Description

Since we're dependent on batch-changes for pr creation now (given it doesn't clone the .git files so we can't create PRs from execution phase) we have to modify the release.yaml. Instead of breaking existing workflows, we're creating a new release.yaml here eventually to be deprecated. I tested this yesterday on the docker repo, and it worked fine, so I'm replicating that here.

It's a direct copy of the release.yaml, except since it's in a subdir, it needs to change the directory sg ops update-images runs from. I also had to remove references to git and gh


Checklist

Test plan

run batch change temporal workflow

@Chickensoupwithrice Chickensoupwithrice requested a review from a team June 25, 2025 23:02
@cloudyadi cloudyadi changed the title feat: add release.yaml specific for batch chanegs feat: add release.yaml specific for batch changes Jun 25, 2025
@Chickensoupwithrice Chickensoupwithrice force-pushed the al/batch-change-release.ymal branch from 6a22c78 to 166e6f0 Compare June 26, 2025 20:45
@Chickensoupwithrice Chickensoupwithrice enabled auto-merge (squash) June 26, 2025 20:45
@Chickensoupwithrice Chickensoupwithrice merged commit 4f0a550 into main Jun 26, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants