Changes to better highlight development-workflow in docs #9473
Conversation
This file contains hidden or 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
|
I killed AppVeyor and Travis as this code doesn't need tests. |
|
FYI, I don't think that adding any information to the pull request template is useful. People just don't read those. |
|
@NelleV ...and it’s often too late at that point ;-) |
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.
PR Summary
The full instructions to use github are at
:ref:development-workflow, but this is not linked indev/Contributingexcept in aseealso::The link in the PR template was there but was just in reference to whether I should create out of a separate branch or not. Of course the link is much more informative than that.
PR Checklist