[Libre-soc-dev] git guide

[Luke Kenneth Casson Leighton]

ok, so the picture i had in my mind for the git guide is:

# what to do if you want to modify some pages

here is the checklist for making changes.  if you do not intend to complete
the work right the way through to "git push" immediately (at least by end
of day), or do not "have time", reconsider and find a way to make the work
smaller.  if unsure, ask on the mailing list.

* run "git pull"
* edit files, making sure only one "purpose"
* save them
* run unit tests and make sure they pass
* fix errors
* run "git status | more", review the output
* run "git diff", review the output
* run "git commit -a -m 'useful description' "
* run "git pull"
* run "git push"

now an explanation of those.

# what to do if "git pull" results in conflict

...
....

# what to do if you want to add files.

...

this one, "git status" is very important, to check files that should have
been added but have not


etc etc etc.



-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68