Automating cutting .latest + main cleanup #70
Merged
Conversation
This file contains 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
emmyoop
changed the title
emmyoop
changed the title
emmyoop
force-pushed
the
er/ct-495-changelog-cleanup
branch
from
90455dd to
7087d50
Compare
leahwicz
reviewed
Jan 27, 2023
leahwicz
reviewed
Jan 27, 2023
leahwicz
approved these changes
Jan 31, 2023
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.
Resolves: dbt-labs/dbt-core#5074
One workflow creates the release branch and cleans up main for a single repo. The other workflow orchestrates doing it for all repositories. The end result is a new branch (typically
1.*.latest) and a PR with all themainbranch cleanup.This is a first pass. It is untested. The workflows need to be in main before they can be tested.