Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix inconsistency of cache-directive vs. docker-cache #38580

Merged
merged 1 commit into from
Mar 28, 2024

Conversation

potiuk
Copy link
Member

@potiuk potiuk commented Mar 28, 2024

This was the same parameter but inconsistently named across the CI/Selective checks. This PR fixes the inconsistency and changes it to docker-cache across the board.


^ 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.

This was the same parameter but inconsistently named across the
CI/Selective checks. This PR fixes the inconsistency and changes it
to `docker-cache` across the board.
@potiuk
Copy link
Member Author

potiuk commented Mar 28, 2024

Unrelated test fails (will fix it in a moment) merging.

@potiuk potiuk merged commit d11a943 into apache:main Mar 28, 2024
60 of 61 checks passed
@potiuk potiuk deleted the fix-cache-directive-inconsistency branch March 28, 2024 10:33
ephraimbuddy pushed a commit that referenced this pull request Jun 5, 2024
This was the same parameter but inconsistently named across the
CI/Selective checks. This PR fixes the inconsistency and changes it
to `docker-cache` across the board.

(cherry picked from commit d11a943)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants