Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[AIRFLOW-XXXX] improve clarity of confirm message #7110

Merged
merged 1 commit into from
Jan 9, 2020

Conversation

dstandish
Copy link
Contributor

@dstandish dstandish commented Jan 9, 2020

Clarifies confirm messaging

Before:

Forcing response 'no' to rebuild CI.

After

Forcing response 'no' to 'rebuild CI?'

Why?

The sentence Forcing response 'no' to rebuild CI can mean "forcing response "no" in order to rebuild CI -- i.e. we must rebuild CI, and to do so, we must force the answer no.

Adding quotes and question mark makes it clear that we are forcing "no" to the question "should we rebuild ci?".


Issue link: Document only change, no JIRA issue

  • Description above provides context of the change
  • Commit message/PR title starts with [AIRFLOW-NNNN]. AIRFLOW-NNNN = JIRA ID*
  • Unit tests coverage for changes (not needed for documentation changes)
  • Commits follow "How to write a good git commit message"
  • Relevant documentation is updated including usage instructions.
  • I will engage committers as explained in Contribution Workflow Example.

* For document-only changes commit message can start with [AIRFLOW-XXXX].


In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.
Read the Pull Request Guidelines for more information.

@dstandish dstandish changed the title AIRFLOW-XXXX improve clarity of confirm message [AIRFLOW-XXXX] improve clarity of confirm message Jan 9, 2020
@potiuk
Copy link
Member

potiuk commented Jan 9, 2020

Adding quotes and question mark makes it clear that we are forcing "no" to the question "should we rebuild ci?".

:D

@potiuk potiuk merged commit d1c7f3c into apache:master Jan 9, 2020
@dstandish dstandish deleted the confirm-dialog branch January 9, 2020 06:58
potiuk pushed a commit that referenced this pull request Jan 21, 2020
kaxil pushed a commit that referenced this pull request Jan 22, 2020
kaxil pushed a commit that referenced this pull request Jan 23, 2020
potiuk pushed a commit that referenced this pull request Jan 26, 2020
kaxil pushed a commit that referenced this pull request Jan 26, 2020
galuszkak pushed a commit to FlyrInc/apache-airflow that referenced this pull request Mar 5, 2020
kaxil pushed a commit to astronomer/airflow that referenced this pull request Mar 30, 2020
(cherry picked from commit d1c7f3c)
(cherry picked from commit 11cc6b5)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants