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 2022/11/22 12:54:05 UTC

[GitHub] [airflow] ephraimbuddy commented on pull request #27829: Improving the release process

ephraimbuddy commented on PR #27829:
URL: https://github.com/apache/airflow/pull/27829#issuecomment-1323635269

   > @ephraimbuddy - the "prepare-provider-documenation" step is added here #27832 - let's see if it works fine. `ANSWER="yes"` is passed from the job environments (see the top of the file) so it should simulate the user answering "yes" to all questions.
   > 
   > I think it will not work, I will have to add some other "bypass" there - becasue there is a question about the type of change as well, but I will add it when I see it (not)working. Something similar you will have to do in your PR, likely for some of the operations. i think it is entirely worthy of the effort - this way you do not have to worry during release if the tool still works or not.
   
   In my case, I wouldn't want to run some commands if the environment is CI, so I'm looking at sorting the commands that would run if `--answer yes` is passed. Or just check if we are on CI and use dry run


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

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org