Skip to content

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented Apr 2, 2024

We already had to do this very sensitive part of the workflow in three places, so it makes sense to extract it to a composite action. This means that we need to do one more checkout from the target branch first (otherwise the action would not be available) but we avoid code duplication and fragility this way.


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
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.

@potiuk potiuk requested review from ashb and kaxil as code owners April 2, 2024 16:40
@potiuk potiuk modified the milestone: Airflow 2.9.0 Apr 2, 2024
We already had to do this very sensitive part of the workflow in
three places, so it makes sense to extract it to a composite
action. This means that we need to do one more checkout from the
target branch first (otherwise the action would not be available)
but we avoid code duplication and fragility this way.
@potiuk potiuk force-pushed the extract-checkout-target-commit-to-composite-action branch from ded8a29 to 04b0029 Compare April 2, 2024 17:09
@potiuk
Copy link
Member Author

potiuk commented Apr 2, 2024

Tested in :

@potiuk potiuk merged commit 76c92c3 into apache:main Apr 2, 2024
@potiuk potiuk deleted the extract-checkout-target-commit-to-composite-action branch April 2, 2024 18:54
@potiuk potiuk added this to the Airflow 2.9.0 milestone Apr 3, 2024
potiuk added a commit that referenced this pull request Apr 3, 2024
We already had to do this very sensitive part of the workflow in
three places, so it makes sense to extract it to a composite
action. This means that we need to do one more checkout from the
target branch first (otherwise the action would not be available)
but we avoid code duplication and fragility this way.

(cherry picked from commit 76c92c3)
@potiuk potiuk added the changelog:skip Changes that should be skipped from the changelog (CI, tests, etc..) label Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools changelog:skip Changes that should be skipped from the changelog (CI, tests, etc..)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants