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

Fix Grammar in PIP warning #13380

Merged
merged 1 commit into from
Dec 30, 2020
Merged

Conversation

kaxil
Copy link
Member

@kaxil kaxil commented Dec 30, 2020

might leads to errors -> might lead to errors


^ Add meaningful description above

Read the Pull Request Guidelines for more information.
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.

`might leads to errors` -> `might lead to errors`
@kaxil kaxil requested a review from XD-DENG December 30, 2020 00:54
@boring-cyborg boring-cyborg bot added area:dev-tools provider:Apache provider:google Google (including GCP) related issues labels Dec 30, 2020
@XD-DENG XD-DENG merged commit 295d66f into apache:master Dec 30, 2020
@github-actions github-actions bot added the okay to merge It's ok to merge this PR as it does not require more tests label Dec 30, 2020
@github-actions
Copy link

The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest master or amend the last commit of the PR, and push it with --force-with-lease.

@kaxil kaxil deleted the fix-grammar-leads branch December 30, 2020 10:05
kaxil added a commit that referenced this pull request Jan 21, 2021
`might leads to errors` -> `might lead to errors`

(cherry picked from commit 295d66f)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:documentation okay to merge It's ok to merge this PR as it does not require more tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants