Skip to content
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

Adds automated generation of provider issue to track test progress #16419

Merged
merged 1 commit into from
Jun 20, 2021

Conversation

potiuk
Copy link
Member

@potiuk potiuk commented Jun 12, 2021

Allows to automatically generate draft of the issue which can be
used to track progress of testing released providers.

@boring-cyborg boring-cyborg bot added area:dev-tools provider:cncf-kubernetes Kubernetes provider related issues area:providers provider:Apache provider:google Google (including GCP) related issues labels Jun 12, 2021
@potiuk potiuk force-pushed the add-issue-generation branch from e01ce44 to e08e5ee Compare June 12, 2021 21:27
@potiuk
Copy link
Member Author

potiuk commented Jun 12, 2021

Fragment of the Issue content generated by this change:

Screenshot 2021-06-12 23 32 40

Screenshot 2021-06-12 23 32 23

@potiuk potiuk force-pushed the add-issue-generation branch 6 times, most recently from d69a0ec to 2386d8e Compare June 13, 2021 00:40
@potiuk potiuk force-pushed the add-issue-generation branch from 2386d8e to 434695d Compare June 13, 2021 11:01
@potiuk potiuk force-pushed the add-issue-generation branch 7 times, most recently from 912f875 to aad8314 Compare June 18, 2021 12:43
@potiuk
Copy link
Member Author

potiuk commented Jun 18, 2021

Hey @ashb @kaxil - regardless of the long-term solution, this is is a very nice automation that helped me to manage the provider issue with status of releases - both the first one and the follow up. It's rather nice IMHO and allows to make it manageable with testing status and pinging people automatically to test the release of providers. It's green, I could merge it :)

@potiuk
Copy link
Member Author

potiuk commented Jun 18, 2021

Saved me couple of hours today already.

BREEZE.rst Show resolved Hide resolved
@potiuk
Copy link
Member Author

potiuk commented Jun 19, 2021

Updated

@github-actions
Copy link

The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease.

@github-actions github-actions bot added the full tests needed We need to run full set of tests for this PR to merge label Jun 19, 2021
@potiuk potiuk closed this Jun 19, 2021
@potiuk potiuk reopened this Jun 19, 2021
@potiuk potiuk force-pushed the add-issue-generation branch 2 times, most recently from a9bc487 to 0af921f Compare June 20, 2021 09:41
Allows to automatically generate draft of the issue which can be
used to track progress of testing released providers.
@potiuk potiuk force-pushed the add-issue-generation branch from 0af921f to 4664b66 Compare June 20, 2021 09:52
@potiuk potiuk merged commit f40d555 into apache:main Jun 20, 2021
@potiuk potiuk deleted the add-issue-generation branch June 20, 2021 14:31
potiuk added a commit to potiuk/airflow that referenced this pull request Jun 22, 2021
…pache#16419)

Allows to automatically generate draft of the issue which can be
used to track progress of testing released providers.

(cherry picked from commit f40d555)
Jorricks pushed a commit to Jorricks/airflow that referenced this pull request Jun 24, 2021
…pache#16419)

Allows to automatically generate draft of the issue which can be
used to track progress of testing released providers.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:dev-tools area:providers full tests needed We need to run full set of tests for this PR to merge provider:cncf-kubernetes Kubernetes provider related issues provider:google Google (including GCP) related issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants