Git Best Practices and Story Process

Git Best Practices

100

Committing to your remote repository at least this often

Daily

200

Do this before you make a commit to make sure it is really completed and passes the pipeline.

Test / Build

300

Never push directly to this branch

Master

400

This should tell a story.

Commit Messages

500

Six Types of Commit Messages

Feat, Fix, Refactor, Docs, Style, Perf, Test, Build, CI, Chore, Revert

Git Implementation

100

You use this to copy a project into your local repository. We use the SSH.

Clone/ Git Clone

200

Used to modify commits interactively.

git rebase -i HEAD 

300

You can spit commits using this series of commands

git rebase -i HEAD{}

edit

git commit --amend

git rebase --continue

Story Process

100

You would use this type of demo to show your team members the implementation of the code and for them to ask any coding questions.

Technical Review/ Technical Demo

200

This would be a demo for the business and the last demo before closing a story

Business Demo/ Demo

300

This is what you should do before scheduling a demo to insure the flow of your presentation

Practice/Test

Jira

100

The sub parts of a story

Task

200

The qualifications that must be met for a story to be considered done

Acceptance Criteria/ AC

MISC.

100

The UI that is used for git project collaboration and version control

Git Lab