Naming agreement

Types of a branch

hotfix - only urgent fixes, should be launched asap, regardless of other branches

feature - all features and fixes, will be launched in a strict order

Types of a task

bug - when any existing element has unexpected/unwanted behaviour (like the subsribe form doesn't work, etc)

feature - any new thing

edit - any improving of existing elements, including modifying (to something new, not due to the wrong behaviour, like styles changing according to the new design, etc)

Structure

Type	Structure	Sample
Ticket name	[type] [name] : [part]	feature home : edits
Ticket content	group by page, element, device	Tented suites - Blog promo : mobile padding should be 20px
Commit name	[related ticket name] | [ticket number]	feature home : edits | AN-1
Bug/edit description	Mozilla way. Name [type] 1. Where and steps to reproduce (if there are) 2. Actual results 3. Expected results with details So just should reply these on these questions : how to see? what's now? what's should be?	Thank you header edit. On the thank you page, h1 header. Now it's the blue h1 header. Should be gray h2 header (#717272, styles like https://dev.angama.com/stay/ "Explore the property")
Feature description	Name [type] 1. Goal of the feature (why) 2. Scheme of the feature (Optional. Can be skipped for simple things) 3. Details So just need to reply on these questions : what? why? details	Post comment form captcha feature. Need to add protection to avoid spam. Vendor for captcha is Google. Last week Wednesday there were about 10 spam comments. (still in live moderation queue)