potiuk opened a new pull request #15518: URL: https://github.com/apache/airflow/pull/15518
The release manager, when reviewing providers to release might make interactive decisions what to do: 1) mark certain provider as 'doc-only' change 2) decide whethere to generate documentation for the provider In case the provider change is marked as 'doc-only' the next time when providers are checked the doc-only change is not seen as 'change' and the provider is automatically skipped. This saves time when preparing subsequent releases of providers as all the "doc-only changes" from the previous release do not have to be re-reviewed (unless there are some new changes). <!-- Thank you for contributing! 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. Feel free to ping committers for the review! In case of existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md). -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
