-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[airbyte-ci] Improved PR generation flow and a bugfix #38582
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good thanks for fixing!
@@ -42,18 +42,23 @@ | |||
default=False, | |||
help="Create a pull request.", | |||
) | |||
|
|||
@click.option( | |||
"--no-bump", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: the negative flag is a little confusing. why not --bump
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had the same thought, but honestly, good enough for an internal tool for now.
One type check failed but given there are 593 of them total and I can't run just one file locally, I'm sorry, I'm merging this so I can easily document how to regen all those PRs. |
What
A batch of changes to
airbyte-ci
that @bleonard and I did to push up the poetry + base image migration PRs.These seem to make sense universally, so I'm pushing them up:
up_to_date
until asked to.pull_request --bump
TODO
This still needs a version bump to airbyte-ci itself.
Can this PR be safely reverted and rolled back?