Commit 75378d5f authored by Toni Beier's avatar Toni Beier

Every sentences on single line

parent 4d9a080f
......@@ -10,7 +10,9 @@ So to deal with these conventions we need to follow some rules so that we don't
Kindly follow up the following directives
## Create a Feature
To create a feature kindly write in first "feature" then use slash '/' to further explain where is the feature and what is the name of feature. So after slash you type in "module name" in which this new feature is being introduced. Then again slash '/' and type in the "name of the feature". Please use underscore '_' in between words if there are two or more words.
To create a feature kindly write in first "feature" then use slash '/' to further explain where is the feature and what is the name of feature.
So after slash you type in "module name" in which this new feature is being introduced. Then again slash '/' and type in the "name of the feature".
Please use underscore '_' in between words if there are two or more words.
An Example would be: feature/public_transport/favorites
......@@ -19,7 +21,9 @@ An Example would be: feature/public_transport/favorites
and "favorites" is the name of the feature.
## Fix an Issue
To fix an issue kindly write in first "fix" then use slash '/' to indicate fix number which would be used with hashtag e.g. "#10". Then again another slash '/' and give the "module name" in which we are making this fix. Further we add another slash '/' and give your fix an "issue name". Please use underscore '_' in between words if there are two or more words.
To fix an issue kindly write in first "fix" then use slash '/' to indicate fix number which would be used with hashtag e.g. "#10".
Then again another slash '/' and give the "module name" in which we are making this fix. Further we add another slash '/' and give your fix an "issue name".
Please use underscore '_' in between words if there are two or more words.
An Example would be: fix/#10/public_transport/swipe_down_to_refresh
......@@ -31,14 +35,16 @@ and "swipe_down_to_refresh" is the name of the issue that we have fixed.
## Release a Version
To release a version kindly write in first "release" then use slash '/' to give the version number and we will do it with a 'v' for a version with the number like '1.5.2'.
So how does these three numbers work?
Version numbers usually consist of three numbers separated by dots. For example: 1.5.2 These numbers have names. The leftmost number (1) is called the major version. The middle number (5) is called the minor version. The rightmost number (2) is called the revision but it may also be referred to as a "point release" or "subminor version".
Version numbers usually consist of three numbers separated by dots.
For example: 1.5.2 These numbers have names. The leftmost number (1) is called the major version. The middle number (5) is called the minor version. The rightmost number (2) is called the revision but it may also be referred to as a "point release" or "subminor version".
An Example would be: release/v1.5.2
## Temporary Branch
Furthermore, we can have temporary (feature | fix | release) branch too. You can put a 'tmp' in front of it to mark this branch as temporary. Please use underscore '_' in between words if there are two or more words.
Furthermore, we can have temporary (feature | fix | release) branch too.
You can put a 'tmp' in front of it to mark this branch as temporary. Please use underscore '_' in between words if there are two or more words.
An Example would be:
* tmp/feature/public_transport/favorites
* tmp/fix/#10/public_transport/swipe_down_to_refresh
* `tmp/fix/#10/public_transport/swipe_down_to_refresh`
* tmp/release/v1.5.2
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment