potiuk commented on pull request #11828:
URL: https://github.com/apache/airflow/pull/11828#issuecomment-718174087


   Shiny-new version! Here is the final description of how it works (note that 
we will not see that behavior here - only after we merge it)! 
   
   All the PRs before approval will run either "small" set of tests (default 
matrix values) or not at all (in case of doc-only changes).
   
   Then interesting things will happen after PR gets approval from the 
committer:
   
   1) The doc-only tests will get "okay to merge" label and this comment: "The 
PR is ready to be merged. No tests are needed!" : 
   
   ![Screenshot from 2020-10-28 
20-41-53](https://user-images.githubusercontent.com/595491/97489713-2f891580-1960-11eb-8ea7-78c2b6c1be8e.png)
   
   
   2) If the PR is not changing "Core" of airflow, the PR will get "okay to 
merge" label and this comment: "The PR should be OK to be merged with just 
subset of tests as it does not modify Core of Airflow. The committers might 
merge it or can add a label 'full tests needed' and re-run it to run all tests 
if they see it is needed!". 
   
   ![Screenshot from 2020-10-28 
20-48-27](https://user-images.githubusercontent.com/595491/97489701-2a2bcb00-1960-11eb-8535-cbb78a3511f2.png)
   
   3) If the PR is changing "Core" of airflow, the PR will get "full tests 
needed" label and this comment:  "This PR requires a full set of tests. Please 
rebase the PR on the latest master or ask a committer to re-run the tests". And 
the "okay to test" label should change to "full tests needed". We will add the 
"in-progress" check, to make the button 'gray' until it gets rebased and the 
full set of tests will run for it. The PRs with this label will run "full 
matrix" tests. 
   
   ![Screenshot from 2020-10-28 
20-49-14](https://user-images.githubusercontent.com/595491/97489686-25ffad80-1960-11eb-9090-7365c0630914.png)
   
   


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


Reply via email to