Open
Conversation
...as this document won't exist in projects' repositories, and has to be generic
Member
|
I enjoyed the Atlassian Centralized vs Gitflow workflow vs. Forking workflow articles and they helped me understand and articulate myself in some confusing interactions I had encountered with other people's git habits. Agree with being parsimonious with the links in general: maybe no need to link to this project's pull requests. That is, I agree with it as you just changed it. |
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.
This adds guidelines for contributors to the Code for Boston GitHub Organization. This guide will be linked to for anyone creating a new PR or Issue on a repository that doesn't have their own template defined.
Image from GitHub's article above:
