Closed yukinoda closed 2 years ago
OLD CONTRIBUTING.md
Following branches should be used for primary code management
master
there can be only this branch. This hold all the latest already released code.master
can be used as stable bleeding edge releasable code.{type}/{GithubIssueNo}-issue-one-liner
should be the format for branch naming
{type}
.{GithubIssueNo}
in Github.Pull requests are the only way to propose a value you want to add. Following is a general workflow for submitting any requests.
master
.master
branchWe have very precise rules over how our git commit messages can be formatted. This leads to more readable messages that are easy to follow when looking through the project history. But also, we use the git commit messages to generate the changelog.
Each commit message consists of a header, a body and a footer. The header has a special format that includes a type, a scope and a subject:
<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
The header is mandatory and the scope of the header is optional.
Any line of the commit message cannot be longer 74 characters! This allows the message to be easier to read on GitHub as well as in various git tools.
Must be one of the following:
src
or test
filesThe scope could be any module name of the commit change. For example Compiler
, ElementInjector
, etc.
The subject contains succinct description of the change:
Just as in the subject, use the imperative, present tense.
-
The footer should contain any information about Breaking Changes and is also the place to reference Github issues that this commit Closes.
Breaking Changes should start with the word BREAKING CHANGE:
with a space or two newlines. The rest of the commit message is then used for this.
add CONTRIBUTING.md for future contributors
Deprecated material-ui contributing guide: https://github.com/monstar-lab-oss/admin-panel-template-reactjs/blob/material-ui-deprecated/CONTRIBUTING.md