docs: expand contributor alternate versions instructions #1435
+12
−8
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.
Situation
The CONTRIBUTING > Alternate versions section describes how to publish Cypress Docker images that are not Primary versions.
The instructions do not make a clear distinction between a "publish" branch and a "working" branch. If misinterpreted, this can lead to premature publishing when working wholly in the parent repo, compared to providing the changes from a fork.
Change
In CONTRIBUTING > Alternate versions make it clearer that 2 branches are needed, and emphasize that no PR should target the
master
branch.Add a suggestion for naming a working branch, that can be used both by Cypress org members and external contributors working from a fork.