Open
Conversation
samporapeli
force-pushed
the
documentation/contributing
branch
from
19c39ac to
218d2dc
Compare
Member
Author
|
Should we add instructions for reviewing changes? How about squash merging into main branch, should that be encouraged? |
Contributor
|
I guess otax/production should be left otax stable. Maybe making a new dev branch, and squash merges from there to master |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
@ilarikuoppala and others, what do you think of these guidelines? Feel free to comment, suggest changes or commit directly to this branch.
Resolves #91