potiuk opened a new pull request, #37057:
URL: https://github.com/apache/airflow/pull/37057
In our process, we generally do not let the scripts in the "build images"
workflow to use `scripts/ci`, `dev` and `action` scripts to come from the PR.
This is a security feature that prevent Pull Requests from forks to run code on
a worker that can potentially access sensitive information - such as
GITHUB_TOKEN with write access to Github Registry.
This, however, causes troubles, because in order to test any changes in
those scripts affecting building image, you have to close your PR from the fork
and push one directly to Apache repository (there in-line build workflows are
used from "Test" workflow and those PRs are safe to run, because only
committers can push directly to the `apache/airflow` repository branches.
This PR changes default behaviour for committer PRs. Rather than do the same
as "regular" PRs, those PRs will not use scripts from the target branch,
instead they will use scripts from the incoming PRs of the committers. This is
equally safe as running PRs from the `apache/airflow` branch - because we have
a reviewed list of committers in our code and "selective checks" job that
checks it is run always in the context and with the code of the "target"
branch, which means that you cannot manipulate the list of actors.
The Girhub actor is retrieved from pull requests github context
(event/pull_request/user/login) so it is impossible to spoof it by the incoming
PR.
As part of this PR - list of available selective checks and documentation of
PR labels and selective checks (wrongly named as "static checks") were reviewed
and updated.
<!--
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/
-->
<!-- 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
[newsfragments](https://github.com/apache/airflow/tree/main/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: commits-unsubscr...@airflow.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
