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 typo in fastsearch comments #14608

Merged
merged 1 commit into from Sep 11, 2019
Merged

fix typo in fastsearch comments #14608

merged 1 commit into from Sep 11, 2019

Conversation

esc
Copy link
Contributor

@esc esc commented Jul 5, 2019

too vs. two vs. to

@the-knights-who-say-ni
Copy link

the-knights-who-say-ni commented Jul 5, 2019

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA).

Unfortunately we couldn't find an account corresponding to your GitHub username on bugs.python.org (b.p.o) to verify you have signed the CLA (this might be simply due to a missing "GitHub Name" entry in your b.p.o account settings). This is necessary for legal reasons before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

You can check yourself to see if the CLA has been received.

Thanks again for your contribution, we look forward to reviewing it!

Copy link
Member

@aeros aeros left a comment

@esc Thanks for the contribution! If you have already signed the CLA over 24 hours ago, try manually updating the status on GitHub. This can be done by clicking on the "check yourself" link posted by the CLA bot @the-knights-who-say-ni. I had to do perform this process for my CLA status to be updated, so I figured it'd be worth mentioning.

Otherwise, it looks like all of the tests are passing, and typo corrections are always welcome. Once the CLA is updated, a core developer will be able to review your PR and potentially have it merged into the repository.

@esc
Copy link
Contributor Author

esc commented Jul 6, 2019

@aeros167 thanks for pointing towards that, but I haven't actually signed it yet, will do that now.

@esc
Copy link
Contributor Author

esc commented Jul 6, 2019

O.K. I have just signed it, now I wait.

@aeros
Copy link
Member

aeros commented Jul 6, 2019

@esc No problem. After the CLA has been verified, feel free to also check out the Python bug tracker for specific issues that could use assistance: https://bugs.python.org/

I'd recommend starting with the ones under the "easy issues" category. Also, another great resource for new contributors is the dev guide: https://devguide.python.org/

@esc
Copy link
Contributor Author

esc commented Jul 8, 2019

Alright, CLA is signed, what next?

@aeros
Copy link
Member

aeros commented Jul 9, 2019

Alright, CLA is signed, what next?

Next, we just have to wait for a core python developer to check out the PR. Usually it takes no longer than a week or so depending on how busy they are. They have to provide the final "stamp of approval" in order for it to be auto-merged into the CPython repository.

Since this is a minor change, they'll probably add the skip news and skip label tags onto the issue, which will allow the bedevere/issue-number and bedevere/news tests to pass. An issue number and news entry is usually required for larger changes, but not for more minor issues such as typo fixing.

Copy link
Contributor

@mangrisano mangrisano left a comment

LGTM.

@esc
Copy link
Contributor Author

esc commented Jul 11, 2019

@mangrisano great! What do I need to do next to get this merged!

@mangrisano
Copy link
Contributor

mangrisano commented Jul 11, 2019

You need to wait for a core-dev.

@brettcannon brettcannon added the docs Documentation in the Doc dir label Jul 11, 2019
@aeros
Copy link
Member

aeros commented Jul 12, 2019

@esc

great! What do I need to do next to get this merged!

As I had said a bit earlier:

Next, we just have to wait for a core python developer to check out the PR.

The changes can't be merged until a core dev approves them. On average, this usually takes around a week or two, but can take longer depending on how busy they are. For more information, see the devguide. I'd recommend reading over the pull request page, but the "Review" section in particular is the most relevant to your question.

@miss-islington
Copy link
Contributor

miss-islington commented Sep 11, 2019

Thanks @esc for the PR, and @matrixise for merging it 🌮🎉.. I'm working now to backport this PR to: 3.8.
🐍🍒🤖

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Sep 11, 2019
(cherry picked from commit 60bba83)

Co-authored-by: Valentin Haenel <esc@users.noreply.github.com>
@bedevere-bot
Copy link

bedevere-bot commented Sep 11, 2019

GH-15933 is a backport of this pull request to the 3.8 branch.

@matrixise
Copy link
Member

matrixise commented Sep 11, 2019

Thank you for your contribution, your PR has been merged into master and will be backported to 3.8.

matrixise pushed a commit that referenced this pull request Sep 11, 2019
(cherry picked from commit 60bba83)

Co-authored-by: Valentin Haenel <esc@users.noreply.github.com>
DinoV pushed a commit to DinoV/cpython that referenced this pull request Sep 12, 2019
websurfer5 pushed a commit to websurfer5/cpython that referenced this pull request Jul 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation in the Doc dir skip issue skip news
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants