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/12/10 18:43:20 UTC

[GitHub] [airflow] mik-laj opened a new pull request #12991: Promote new flags in ./docs/build_docs.py

mik-laj opened a new pull request #12991:
URL: https://github.com/apache/airflow/pull/12991


   Not everyone is aware that we have divided the documentation and now it is possible to build documentation for only one package, which is much faster. I am adding messages encouraging them to take advantage of these options to let more people know about it.
   
   I also hope to reduce the number of failed builds on CI if users can quickly test their changes locally. Previously, building documentation took too long for anyone to want to do it locally.
   
   Sample message from a user who was unaware of this flag.
   
   > I gave up on building the doc locally as it seems to take a really long, so I create the PR first to see if it can go through the CI. I will build it locally again if it's necessary. Do you have any tips on speeding up the building process? (edited) 
   
   https://apache-airflow.slack.com/archives/CJ1LVREHX/p1607063305069700
   
   <!--
   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] github-actions[bot] commented on pull request #12991: Promote new flags in ./docs/build_docs.py

Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on pull request #12991:
URL: https://github.com/apache/airflow/pull/12991#issuecomment-742745055


   The PR is likely ready to be merged. No tests are needed as no important environment files, nor python files were modified by it. However, committers might decide that full test matrix is needed and add the 'full tests needed' label. Then you should rebase it to the latest master or amend the last commit of the PR, and push it with --force-with-lease.


----------------------------------------------------------------
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] mik-laj merged pull request #12991: Promote new flags in ./docs/build_docs.py

Posted by GitBox <gi...@apache.org>.
mik-laj merged pull request #12991:
URL: https://github.com/apache/airflow/pull/12991


   


----------------------------------------------------------------
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