mirror of
https://github.com/BlueWallet/BlueWallet.git
synced 2024-11-19 01:40:12 +01:00
DOC: Update CONTRIBUTING.md
This commit is contained in:
parent
be1fca841f
commit
d0a8bcd0e7
@ -1,9 +1,13 @@
|
||||
## Commits
|
||||
|
||||
All commits should have one of the following prefixes: REL, FIX, ADD, REF, TST, OPS, DOC. For example `"ADD: new feature"`.
|
||||
Adding new feature is ADD, fixing a bug is FIX, something related to infrastructure is OPS etc. REL is for releases, REF is for
|
||||
refactoring, DOC is for changing documentation (like this file).
|
||||
|
||||
Commits should be atomic: one commit - one feature, one commit - one bugfix etc.
|
||||
|
||||
## Releases
|
||||
|
||||
When you tag a new release, use the following example:
|
||||
`git tag -m "REL v1.4.0: 157c9c2" v1.4.0 -s`
|
||||
You may get the commit hash from git log. Don't forget to push tags `git push origin --tags`
|
||||
@ -14,6 +18,10 @@ When tagging a new release, make sure to increment version in package.json and o
|
||||
In the commit where you up version you can have the commit message as
|
||||
`"REL vX.X.X: Summary message"`.
|
||||
|
||||
## Guidelines
|
||||
|
||||
Do *not* add new dependencies. Bonus points if you manage to actually remove a dependency.
|
||||
|
||||
All new files must be in typescript. Bonus points if you convert some of the existing files to typescript.
|
||||
|
||||
New components must go in `components/`. Bonus points if you refactor some of old components in `BlueComponents.js` to separate files.
|
||||
|
Loading…
Reference in New Issue
Block a user