You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2020/10/10 08:12:32 UTC
[GitHub] [airflow] mlgruby opened a new pull request #11390: Strict type check for google ads and cloud hooks
mlgruby opened a new pull request #11390:
URL: https://github.com/apache/airflow/pull/11390
Strict type check for google ads and cloud hooks. Part of: #9708
@kaxil & @mik-laj request for review here!
70.651528 google ====================> from 69 to 70 :D
<!--
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 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/
-->
---
**^ Add meaningful description above**
Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)** for more information.
In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+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 [UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md).
----------------------------------------------------------------
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
[GitHub] [airflow] kaxil merged pull request #11390: Strict type check for google ads and cloud hooks
Posted by GitBox <gi...@apache.org>.
kaxil merged pull request #11390:
URL: https://github.com/apache/airflow/pull/11390
----------------------------------------------------------------
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
[GitHub] [airflow] github-actions[bot] commented on pull request #11390: Strict type check for google ads and cloud hooks
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on pull request #11390:
URL: https://github.com/apache/airflow/pull/11390#issuecomment-706512416
[The Workflow run](https://github.com/apache/airflow/actions/runs/298924025) is cancelling this PR. It has some failed jobs matching ^Pylint$,^Static checks$,^Build docs$,^Spell check docs$,^Backport packages$,^Checks: Helm tests$,^Test OpenAPI*.
----------------------------------------------------------------
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
Re: [GitHub] [airflow] mlgruby opened a new pull request #11390:
Strict type check for google ads and cloud hooks
Posted by Michael Crawford <mi...@modernizingmedicine.com>.
unsubscribe
On Sat, Oct 10, 2020 at 4:12 AM GitBox <gi...@apache.org> wrote:
>
> mlgruby opened a new pull request #11390:
> URL: https://github.com/apache/airflow/pull/11390
>
>
> Strict type check for google ads and cloud hooks. Part of: #9708
>
> @kaxil & @mik-laj request for review here!
>
> 70.651528 google ====================> from 69 to 70 :D
> <!--
> 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 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/
> -->
>
> ---
> **^ Add meaningful description above**
>
> Read the **[Pull Request Guidelines](
> https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)**
> for more information.
> In case of fundamental code change, Airflow Improvement Proposal ([AIP](
> https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+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
> [UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md).
>
>
>
> ----------------------------------------------------------------
> 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
>
>
>
--
MICHAEL CRAWFORD
DATA WAREHOUSE & ENGINEERING MANAGER
C: 601-310-7383
E: michael.crawford@modmed.com
[image: [ Modernizing Medicine ]] <https://www.modmed.com/>
[image: [ Facebook ]] <https://www.facebook.com/modernizingmedicine> [image:
[ LinkedIn ]] <https://www.linkedin.com/company/modernizing-medicine/> [image:
[ YouTube ]] <https://www.youtube.com/user/modernizingmedicine> [image: [
Twitter ]] <https://twitter.com/modmed> [image: [ Blog ]]
<https://www.modmed.com/BlogBeyondEMR> [image: [ Instagram ]]
<https://instagram.com/modernizing_medicine>
--
*CONFIDENTIALITY NOTICE:* This e-mail message may contain material
protected by the Health Insurance Portability and Accountability Act of
1996 and its implementing regulations and other state and federal laws and
legal privileges. This message is only for the personal and confidential
use of the individuals or organization to whom the message is addressed. If
you are an unintended recipient, you have received this message in error,
and any reading, distributing, copying or disclosure is unauthorized and
strictly prohibited. All recipients are hereby notified that any
unauthorized receipt does not waive any confidentiality obligations or
privileges. If you have received this message in error, please notify the
sender immediately at the above email address and confirm that you have
deleted or destroyed the message.