Thomas Burleson, Solutions Architect Copyright 2022 - All rights reserved Knowledge Pyramid The illustration below highlights the layered training process used to scale teams to Enterprise Git Best Practices: Git Guidelines: Pull Requests Developers are often confused by the concept of Git Pull Requests. While the concept is simple, team often struggle with Pull Requests (PRs). There are, however, best practices that will ensure your PR process is pain-free and clean. Use recommended GitFlow Feature Branches.

GitOps - Contributing Changes We would love for you to contribute to our project and help make it even better than it is today! As a contributor, here are the guidelines we would like you to follow: Commit Conventions GitFlow Feature Branches Pull Requests Squashing and Rebasing Code Reviews

GitOps - Customized Git Normal git logs commands will output a full log detail to the console: Often developers want to see compacted, colorized log outputs. To generate the compact logs, use a custom git lg command. Developers should create a git alias in their git configuration file: ~/.gitconfig [alias] plog = log --color --graph --pretty=format:'%C(red)%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit

Authors: Thomas Burleson, Solutions Architect Copyright 2021 - All rights reserved GitOps: Top 10 Rules Using Git properly is essential for successful web-application development and CI/CD. The best practices for GitFlow have been codified and condensed into 10 Essential Rules: Use GitFlow strategies