airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] feluelle opened a new pull request #4161: [AIRFLOW-3315] Add ImapAttachmentSensor
Date Thu, 08 Nov 2018 14:09:31 GMT
feluelle opened a new pull request #4161: [AIRFLOW-3315] Add ImapAttachmentSensor
   Make sure you have checked _all_ steps below.
   ### Jira
   - [x] My PR addresses the following [Airflow Jira](
issues and references them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
     - 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.
   ### Description
   - [x] Here are some details about my PR, including screenshots of any UI changes:
   This PR adds a sensor that pokes a mail server for attachments in mails with a given name.
   If an attachment has been found it will immediately stop and return that an attachment
has been found for the given name.
   **This PR also updates the license header in imap_hook and test_imap_hook**
   ### Tests
   - [x] My PR adds the following unit tests __OR__ does not need testing for this extremely
good reason:
   This PR adds tests for:
   * test_poke_with_attachment_found
   * test_poke_with_attachment_not_found
   * test_poke_with_check_regex_true (tests if `check_regex=True` will be passed to the Hook's
   * test_poke_with_different_mail_folder (tests a mail folder other than `INBOX`)
   ### 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](":
     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
     - When adding new operators/hooks/sensors, the autoclass documentation generation needs
to be added.
   ### Code Quality
   - [x] Passes `flake8`

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

View raw message