It is better to have many branches each being limited to a particular topic rather than a single branch doing lots of things. Only merge complete and tested work back onto the master branch.Įach development branch must have a precise and limited scope (a single web page for example). When work on a branch is complete and tested, the commits on that branch are merged back on to the master branch and the development branch is deleted. If development work takes place (for example developing a new web page) this always happens on a separate branch taken from the most recent commit point on the master branch (as we did with dev-01-intro and dev-02-about) in the previous examples. The master branch only ever contains deployable code. ![]() I only have one main branch, the master branch. Tend to use a simple branching workflow (it is suitable for small teams). I’ve done this by modifying line 30 I’ve added a colour declaration: I’ve changed the colour of the h3 element it’s blue like the Victoria Line. Margin-bottom: 1.2rem /* THIS SETS PARAGRAPH SPACING */Ĭode 2.6 style.css modified in dev-01-intro ![]() ![]() H1, h2, h3, h4, h5, h6 /* format cover image */ Background-color: #fbfaf6 /* Set cream page bkgrd */īackground-color: #fff /* make content area bkgrd white */
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |