justinpakzad opened a new pull request, #76695:
URL: https://github.com/apache/airflow/pull/76695
<!-- 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
-->
---
Follow up to #76243. The fork CI setup in the contributing docs has
contributors sync their main via gh repo sync, and breeze ci audit suggests it
again once main falls 200 commits behind. That sync counts as a push, so these
push workflows would still run in the fork:
- `update-constraints-on-push.yml` (took around 20 mins before failing)
- `java-sdk-dependency-security.yml`
- `milestone-tag-assistant.yml`
- `automatic-backport.yml`
- `notify-uv-lock-conflicts.yml`
This adds a `github.repository == 'apache/airflow'` guard to each so they're
skipped in forks.
CodeQL also runs on sync and just rescans code that was already scanned
upstream. I left it out since it's security tooling and wanted to check first,
but happy to add it in if needed. Note - not all of these fail, some finish
relatively quickly, but I don't believe they need to be running in a user's
fork.
The following were all triggered after running sync on my fork:
- [Update
constraints](https://github.com/justinpakzad/airflow/actions/runs/42416011937)
- [Java SDK dependency
security](https://github.com/justinpakzad/airflow/actions/runs/42416011839)
- [Milestone Tag
Assistant](https://github.com/justinpakzad/airflow/actions/runs/42416011859)
- [Automatic
Backport](https://github.com/justinpakzad/airflow/actions/runs/42416011946)
- [Notify uv.lock
conflicts](https://github.com/justinpakzad/airflow/actions/runs/42416011851)
##### 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 (Claude Opus 5.5)
<!--
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]
