Skip to content

[AIRFLOW-5839] Upgrade pre-commit and hooks to latest versions#6492

Merged
potiuk merged 1 commit into
apache:masterfrom
PolideaInternal:upgrade-latest-pre-commits
Nov 4, 2019
Merged

[AIRFLOW-5839] Upgrade pre-commit and hooks to latest versions#6492
potiuk merged 1 commit into
apache:masterfrom
PolideaInternal:upgrade-latest-pre-commits

Conversation

@potiuk
Copy link
Copy Markdown
Member

@potiuk potiuk commented Nov 4, 2019

We want to use latest pre-commit version as well as latest
version of the plugins used.

Make sure you have checked all steps below.

Jira

  • My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"
    • https://issues.apache.org/jira/browse/AIRFLOW-XXX
    • In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.
    • In case you are proposing a fundamental code change, you need to create an Airflow Improvement Proposal (AIP).
    • In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

Description

  • Here are some details about my PR, including screenshots of any UI changes:

Tests

  • My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

  • My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
    1. Subject is separated from body by a blank line
    2. Subject is limited to 50 characters (not including Jira issue reference)
    3. Subject does not end with a period
    4. Subject uses the imperative mood ("add", not "adding")
    5. Body wraps at 72 characters
    6. Body explains "what" and "why", not "how"

Documentation

  • In case of new functionality, my PR adds documentation that describes how to use it.
    • All the public functions and the classes in the PR contain docstrings that explain what it does
    • If you implement backwards incompatible changes, please leave a note in the Updating.md so we can assign it to a appropriate release

We want to use latest pre-commit version as well as latest
version of the plugins used.
@potiuk potiuk requested review from kaxil and mik-laj November 4, 2019 08:39
@potiuk potiuk self-assigned this Nov 4, 2019
@potiuk potiuk merged commit bb01616 into apache:master Nov 4, 2019
potiuk added a commit that referenced this pull request Nov 4, 2019
We want to use latest pre-commit version as well as latest
version of the plugins used.

(cherry picked from commit bb01616)
potiuk added a commit that referenced this pull request Nov 12, 2019
We want to use latest pre-commit version as well as latest
version of the plugins used.

(cherry picked from commit bb01616)
eladkal pushed a commit to eladkal/airflow that referenced this pull request Dec 2, 2019
…e#6492)

We want to use latest pre-commit version as well as latest
version of the plugins used.

(cherry picked from commit bb01616)
kaxil pushed a commit that referenced this pull request Dec 12, 2019
We want to use latest pre-commit version as well as latest
version of the plugins used.

(cherry picked from commit bb01616)
@potiuk potiuk added the area:production-image Production image improvements and fixes label Apr 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:production-image Production image improvements and fixes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants