-
Notifications
You must be signed in to change notification settings - Fork 42
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
The big documentation and development upgrade #1278
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e action setup instructions
…e action setup instructions yaml link
… not working otherwise
… issue activating venv
… environment properly configured
Because rebasing was very painful upgrading from here #1319 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the one we will merge whenever we want to. I am only perfecting things at this point.
Supersedes all others as they are so coupled changes and are hard to break down into smaller bits eg. #1238
First stage implementation of #1148
Could I propose maybe we do this merge independently of 2.6 but before 2.6? Or the documentation upgrade becomes 2.6 and the further upgrades become 2.7?
I just realised I should open this only when pre/2.6 branch is open and maybe only when 2.5 is fully done? Seems like an easy base change whenever we decide.