Def: contents of project's .git directory and nothing else

git ls-remote [remote]: get full list of remote references

git remote show [remote]: get list of remote branches

git fetch origin: Fetches changes do not have from the remote and update ur local repo - moving origin/master pointer to its new (up-to-date) position

git push origin serverfix: Take my serverfix local branch and push it to update the remote's serverfix branch

git push origin serverfix:serverfix: Take my serverfix and make it the remote's serverfix

Single collaboration model (centralized workflow)

If suitable, create a repo, and give every developer push access

Include a canonical repo, that represents the offical project

Each dev-er has write-access to their own public repo. and read-access to everyone else's

Dev-ers make their own public clone of the project and push changes to it

❗Then they inform the maintainer of the main project to pull their changes

The maintainer add dever's repo as a remote, test changes locally merge them into the branch and push back to their repo

Contributors do not have to wait for the project to incorporate their changes - each can work on their pace

Lieutenants: various integration managers are in charge of certain parts of the repo

he pushes from his directory to a reference repository ffrom which all the collab need to pull

Allows project leader (the dictator) to delegate much of the work and collect large subsets of the code at multiple points before integrating them

run git diff --check before commits to identify and list possible white space errors

ignore warning: git config apply.whitespace nowarn

Centralized workflow with offline committing and simple branching and merging

Pros: Fastest protocol, allow anonymous public access

Cons: Difficult to setup, lack of authentication, use non standard port (9418) which can be blocked

Audit log: records all events that have happended at the organization level, who did them and where in the world they were done