Fix bugs introduced when moving the code of issue generation to breeze #28683
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
eladkal
approved these changes
Jan 2, 2023
Member
Author
|
Let's see if it will work :) |
The apache#28352 introduced subtle bugs which failed when runnint it during provider generation. Also added running the command automatically in CI.
potiuk
force-pushed
the
fix-bugs-introduced-in-migrating-issue-generation-command
branch
from
65f5993 to
f132493
Compare
Member
Author
|
Also added a flag to remove progress - it was producing far too long log in CI |
potiuk
deleted the
fix-bugs-introduced-in-migrating-issue-generation-command
branch
64 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
The #28352 introduced subtle bugs which failed when runnint it during provider generation.
Also added running the command automatically in CI.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.