amoghrajesh opened a new pull request, #52407:
URL: https://github.com/apache/airflow/pull/52407
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
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 an 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/
-->
Added some intelligence to classify things before hand for trivial cases. I
already had a `_is_test_or_example_dag_only_changes` in place which did some of
the work but not entirely.
For example:
PR https://github.com/apache/airflow/pull/51107/files is included in tagging
though it's only docs/tests
The PR linked above had
`['providers/google/docs/operators/cloud/kubernetes_engine.rst',
'providers/google/tests/system/google/cloud/kubernetes_engine/example_kubernetes_engine_ray.py']`
which is doc and tests.
our current rules are:
- tests to Skip
- docs to doc-only templating
which I guess is why we didn't catch the automation and asked RM to classify
So the idea here is to do this automatically. We check for precedence here,
if docs and `test_or_example` are present, docs has higher precedence.
Overall precedence order is:
ask > doc-only > skip.
Added some tests that can help.
<!-- Please keep an empty line above the dashes. -->
---
**^ Add meaningful description above**
Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information.
In case of fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+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 a
newsfragment file, named `{pr_number}.significant.rst` or
`{issue_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
--
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]
