CCF_100/InfiniTime
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix various typos

Browse Source 
Found via `codespell -q 3 -S ./src/libs -L ans,doubleclick,trough`
This commit is contained in:
luz paz
2022-05-31 15:17:36 -04:00
committed by Riku Isokoski
parent 7f45538eb5
commit 03a510bd18
21 changed files with 45 additions and 45 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/branches.md
View File

@@ -5,7 +5,7 @@ The project is based on 2 main branches:
- **master** : this branch is always ready to be deployed. It means that at any time, we should be able to build the branch and release a new version of the application.
- **develop** : this branch contains the latest development that will be integrated in the next release once it's considered as stable.
New features should be implemented in **feature branches** created from **develop**. When the feature is ready, a pull-request is created and it'll be merge into **develop** when it is succesfully reviewed and accepted.
New features should be implemented in **feature branches** created from **develop**. When the feature is ready, a pull-request is created and it'll be merge into **develop** when it is successfully reviewed and accepted.
To release a new version of the application, when develop is considered stable, a **release** branch is created from **develop**. This can be considered as a *release candidate* branch. When everything is OK, this release branch is merged into **master** and the release is generated (a tag is applied to git, the release note is finalized, binaries are built,...) from **master**.