Skip to content

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

Closed
wants to merge 0 commits into from
Closed

Conversation

jeromefv
Copy link
Contributor

@jeromefv jeromefv commented Nov 2, 2020

PR Summary

PR Checklist

  • Has pytest style unit tests (and pytest passes).
  • Is Flake 8 compliant (run flake8 on changed files to check).
  • New features are documented, with examples if plot related.
  • Documentation is sphinx and numpydoc compliant (the docs should build without error).
  • Conforms to Matplotlib style conventions (install flake8-docstrings and run flake8 --docstring-convention=all).
  • New features have an entry in doc/users/next_whats_new/ (follow instructions in README.rst there).
  • API changes documented in doc/api/next_api_changes/ (follow instructions in README.rst there).

@story645 story645 marked this pull request as draft November 2, 2020 20:09
@jeromefv
Copy link
Contributor Author

jeromefv commented Nov 7, 2020

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.

@jeromefv
Copy link
Contributor Author

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.

@jeromefv jeromefv force-pushed the getting_started branch 2 times, most recently from bbebb16 to e3b45ec Compare November 16, 2020 21:31
@jeromefv jeromefv marked this pull request as ready for review December 2, 2020 19:19
@jeromefv jeromefv requested a review from story645 December 3, 2020 00:53
@brunobeltran brunobeltran added this to the v3.4.0 milestone Dec 23, 2020
@jeromefv
Copy link
Contributor Author

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.

@story645
Copy link
Member

Is alright, git is a massive pain. Ping on gitter as needed!

@jklymak
Copy link
Member

jklymak commented Dec 24, 2020

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.

@jeromefv jeromefv closed this Dec 28, 2020
@story645 story645 mentioned this pull request Dec 28, 2020
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants