From commits-return-64256-archive-asf-public=cust-asf.ponee.io@airflow.apache.org Mon Sep 2 00:05:36 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 72B5A180668 for ; Mon, 2 Sep 2019 02:05:36 +0200 (CEST) Received: (qmail 99433 invoked by uid 500); 2 Sep 2019 00:05:35 -0000 Mailing-List: contact commits-help@airflow.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airflow.apache.org Delivered-To: mailing list commits@airflow.apache.org Received: (qmail 99424 invoked by uid 99); 2 Sep 2019 00:05:35 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Sep 2019 00:05:35 +0000 From: GitBox To: commits@airflow.apache.org Subject: [GitHub] [airflow] potiuk opened a new pull request #5977: [AIRFLOW-5371] Remove yamllint as prerequisite to run pre-commit Message-ID: <156738273555.27609.16016270798245961999.gitbox@gitbox.apache.org> Date: Mon, 02 Sep 2019 00:05:35 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit potiuk opened a new pull request #5977: [AIRFLOW-5371] Remove yamllint as prerequisite to run pre-commit URL: https://github.com/apache/airflow/pull/5977 Make sure you have checked _all_ steps below. ### Jira - [ ] My PR addresses the following [Airflow Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR" - https://issues.apache.org/jira/browse/AIRFLOW-5371 ### Description - [x] Here are some details about my PR, including screenshots of any UI changes: No yamllint needs to be installed in host to run pre-commits. ### Tests - [x] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason: ### Commits - [x] 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](http://chris.beams.io/posts/git-commit/)": 1. Subject is separated from body by a blank line 1. Subject is limited to 50 characters (not including Jira issue reference) 1. Subject does not end with a period 1. Subject uses the imperative mood ("add", not "adding") 1. Body wraps at 72 characters 1. Body explains "what" and "why", not "how" ### Documentation - [x] 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](https://github.com/apache/airflow/blob/master/UPDATING.md) so we can assign it to a appropriate release ### Code Quality - [x] Passes `flake8` ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: users@infra.apache.org With regards, Apache Git Services