dchaplinsky commented on issue #4891: [AIRFLOW-4067] Telegram hook/operator to post messages to telegram channels URL: https://github.com/apache/airflow/pull/4891#issuecomment-471611817 No problem I understand your intention to keep everything highly organized. Little Q. Should I add hook/operator into contib section of API docs? If so, I'll need to move imports of telegram bindings from global scope to methods, otherwise documentation won't build without python-telegram-api On Mon, Mar 11, 2019 at 3:08 PM Xiaodong <[email protected]> wrote: > @dchaplinsky <https://github.com/dchaplinsky> please update your PR > description based on the original template (ref: #4890 > <https://github.com/apache/airflow/pull/4890>) > > You may find it tedious. But this make it easier for folks to understand > what you're trying to propose in this PR, and easily link to JIRA. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/apache/airflow/pull/4891#issuecomment-471531067>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AAIAcp-b_asHGDvLjtlDMK33Kqgzz-Dnks5vVlVRgaJpZM4bnTS4> > . >
---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services
