Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Document git repo best practices #10

Open
JPrevost opened this issue Mar 24, 2017 · 3 comments
Open

Document git repo best practices #10

JPrevost opened this issue Mar 24, 2017 · 3 comments
Assignees
@JPrevost

Comments

@JPrevost
Copy link
Member

No description provided.

@JPrevost JPrevost self-assigned this Mar 24, 2017
@JPrevost
Copy link
Member Author

partially addressed in MITLibraries/mitlibraries.github.io#16 but include stuff like codeclimate, travis, coveralls as normal for most dev projects.

@gravesm
Copy link

gravesm commented Nov 8, 2018

The current docs suggest to include administrators when protecting branches, but this means a new review is required when squashing before a merge.

@hakbailey
Copy link
Contributor

What @gravesm said. Let's not require that, since we are expecting folks to squash before merging.

@JPrevost JPrevost transferred this issue from MITLibraries/mitlibraries.github.io Dec 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JPrevost JPrevost

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@gravesm @JPrevost @hakbailey