04 - Working with Git for Enterprise DevOps Flashcards
Monorepo vs multiple repo
Monorepo is per team
Repository is place where history of your work is stored
Azure DevOps projects can contain multiple repositories
Why implement a change log
To track changes to a project over versions
Feature branching
feature development in dedicated branch instead of mater branch
GitFlow branching
strict branching model designed around the project release
Forking workflow
every developer uses a server-side repository
Evaluate the workflow
does workflow scale?
is it easy to un-do mistakes?
does workflow impose any new unnecessary cognitive overhead to team?
Cognitive overhead
How much do you have to think about doing something, i.e. using Facebook is intuitive, doesn’t require training.
GitFlow branch workflow
Great for release-based software workflow
Offers dedicated channel for hotfixes to production
Forking workflow
Gives every developer their own server-side repository
Has two Git repositories, one private local, and one public server-side
fill in
Git Hub mobile for pull request approvals
fill in
Git hooks
fill in
Fostering inner source
fill in
Inner source
Brings all the benefits of open-source software development inside your firewall
Large repositories
Caused by long history and large binary files
Purge repository data
Reduce repository size
Remove accidentally committed large fine
Remove committed file with sensitive data (passwords, keys)
