You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to make it as easy as possible for anyone to contribute their stuff, I would like to write a guide document to tell them how to do so.
This document would include a brief primer on git and github, explain how to properly organize their work into commits, branches, and how to utilize pull requests, as well as examples for feature requests and bug reports, to make sure they provide all necessary information.
How to write commit messages and what to put into a commit is one of those topics among programmers. We love to pull each others hairs out over it. It's almost as bad as spaces vs tabs. The only way to get around this is to propose clear guidelines for a project, that everyone adheres to. Changes to these guidelines should be made in a pull request and extensively discusses and considered.
The text was updated successfully, but these errors were encountered:
In order to make it as easy as possible for anyone to contribute their stuff, I would like to write a guide document to tell them how to do so.
This document would include a brief primer on git and github, explain how to properly organize their work into commits, branches, and how to utilize pull requests, as well as examples for feature requests and bug reports, to make sure they provide all necessary information.
How to write commit messages and what to put into a commit is one of those topics among programmers. We love to pull each others hairs out over it. It's almost as bad as spaces vs tabs. The only way to get around this is to propose clear guidelines for a project, that everyone adheres to. Changes to these guidelines should be made in a pull request and extensively discusses and considered.
The text was updated successfully, but these errors were encountered: