-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Getting Started GSoD #18873
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
Getting Started GSoD #18873
Conversation
Ah, it appears as though I had commits from other contributors from the upstream included. I'm not quite sure how to deal with those at the moment. |
9abbf92
to
f0712dc
Compare
I think what I had tried to do made it much messier with all of the items in Files Changed from the soft reset of commits. |
bbebb16
to
e3b45ec
Compare
e56b3fb
to
b4c4ae0
Compare
cc756c3
to
91ee54a
Compare
Ugh, I knew I messed up again... I couldn't remember how to rebase properly with my original local branch and now it's back to the messed up problem I had before. I apologize for dropping the ball on this PR. |
Is alright, git is a massive pain. Ping on gitter as needed! |
Until you know what you are doing, always back your branch up before doing a rebase. Then you can repeat until you get it right. |
91ee54a
to
0520035
Compare
PR Summary
PR Checklist
pytest
passes).flake8
on changed files to check).flake8-docstrings
and runflake8 --docstring-convention=all
).doc/users/next_whats_new/
(follow instructions in README.rst there).doc/api/next_api_changes/
(follow instructions in README.rst there).