shahar1 opened a new pull request, #70356:
URL: https://github.com/apache/airflow/pull/70356
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull
request.
Write a good git commit message following this guide:
https://chris.beams.io/posts/git-commit/
Please make sure that your code changes are covered with tests.
And in case of new features or big changes remember to adjust the
documentation.
For user-facing UI changes, please attach before/after screenshots (or a
short
screen recording) so reviewers can assess the visual impact.
Feel free to ping (in general) for the review if you do not see reaction for
a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we
sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: #ISSUE
-->
## Human Summary
This PR improves the flow of creating the github issue and carrying over the
checkmarks as part of the providers release.
## AI Summary
<details><summary>Click here</summary>
This pull request updates the provider release workflow documentation in
`dev/README_RELEASE_PROVIDERS.md` to clarify and improve the process for
generating, editing, and publishing provider testing issues on GitHub. The main
focus is on making the workflow more robust against GitHub's URL length
limitations, supporting local editing, and ensuring checkmarks are properly
carried over between waves.
**Documentation improvements to provider issue workflow:**
* Recommends generating the provider testing issue body locally to a file
(`files/provider_issue.md`) before publishing, allowing for local modifications
and avoiding GitHub URL length limitations.
* Adds clear instructions for filtering out noisy PRs from the generated
issue using the `--excluded-pr-list` option.
* Documents how to carry over completed checkmarks from the previous wave’s
issue, including platform-specific `sed` commands for macOS and GNU/Linux.
* Details the steps for creating or updating the GitHub issue from the local
file, including how to update an existing issue with the carried-over
checkmarks.
* Improves overall workflow clarity and robustness by breaking the process
into clear steps and emphasizing the importance of local file editing before
publishing.
[[1]](diffhunk://#diff-1ef4f02ce0e55bffd7245e78c55bd83bfab647c6d4e6c8dc7925405398871371L828-R860)
[[2]](diffhunk://#diff-1ef4f02ce0e55bffd7245e78c55bd83bfab647c6d4e6c8dc7925405398871371R870-R906)
</details>
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change below checkbox to `[X]` followed by the name of the tool, uncomment
the "Generated-by".
-->
- [x] Yes (please specify the tool below)
<!--
Generated-by: [Tool Name] following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
-->
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
