Forward Pay

Favor Tracking - React application

32549 Advanced Internet Programming - Spring 2020

Postgraduate Tutorial 01

Git Conventions

Git Messages

Philosophy based off of Emoji-Log: A new way to write Git commit messages

1. Imperative
   • Commit messages should be imperative, like you are giving an order
     ✅ Add instead of ❌ Added
     ✅ Create instead of ❌ Creating
2. Categories
   • Each commit starts with a category,
     📦 NEW:
     👌 IMPROVE:
     🐛 FIX:
     📖 DOC:
     🚀 RELEASE:
     ☑️ TEST:
     🥨 REFACTOR:
3. Actions
   • Each commit is based on actions you take
4. Spelling
   • Use proper spelling where possible
5. Capitalisation
   • The categories should be all UPPERCASE followed by a single colon :
   • The first letter of the first word following the colon should be capitalised
   • Following letters should be all lowercase UNLESS
     • A proper noun
     • Referring specifically to filename, class, method, function or other specific part of the coded project

No branches just origin/master unless you are willing to deal with the issues of branch merge directly

Expected steps

1. Add all files to local
2. Commit directory/project to local
3. Pull Remote
   1. Resolve Issues
   2. Re Commit Local
4. Push Local to Remote

If there are any unexpected errors do communicate with rest of team when working.

Do Steps When

1. Before Work Starts
2. Periodically
   1. Any significant changes
   2. Work on other Projects
   3. Return From Working on other projects
   4. Need to move away from keyboard
   5. Come back to working after being away
   6. Use your own judgement
3. End of the day / When done with work