-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Editing "issues for new contributors" #23602
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
Editing "issues for new contributors" #23602
Conversation
I am very 👍🏻 on this modulo those comments. Strongly suspect that rebasing on main will fix the build issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a rebase won't fix doc build, because of the following:
Thanks for the useful comments! I will fix it up. 🙇 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this addition. I suppose it is hard to distinguish "medium" and "hard" here and we don't want to explicitly break those categories out because there may be some gray area between them?
Yeah, I imagine this is the reason it was like this before. I am not certain how to distinguish them at this time. |
This PR edits clarifies the reasons
Difficulty: Medium
andDifficulty: Hard
labels might be added.It is based on conversations arising in the new contributor meeting.
Feedback is welcome!
PR Checklist
Tests and Styling
pytest
passes).flake8-docstrings
and runflake8 --docstring-convention=all
).Documentation
doc/users/next_whats_new/
(follow instructions in README.rst there).doc/api/next_api_changes/
(follow instructions in README.rst there).