GitGraph Diagrams

What are GitGraph Diagrams?

Mermaid's GitGraph diagrams help you visualize Git workflows and branching strategies. For data teams, they're invaluable for documenting:

  • Feature development workflows

  • Release processes

  • Data pipeline versioning

  • Model deployment strategies

  • Hotfix procedures

  • Team collaboration patterns


Creating Your First GitGraph

  1. Launch DinoAI: From Code IDE, access DinoAI to start creating diagrams.

  2. Use a Simple Prompt: Tell DinoAI what kind of Git Graph Diagram you want to create. For example:

- "Create a mermaid GitGraph showing my feature branch workflow for data model development"

- "Generate a mermaid GitGraph diagram for my dbtβ„’ release process with main, develop, and feature branches"

- "Build a mermaid Git workflow diagram showing my data team's branching strategy and merge process"
  1. Get Your Diagram: DinoAI will generate a complete .mmd file with proper Mermaid syntax.

  2. Preview Your Work: Click the eye icon (πŸ‘οΈ) to preview your diagram in real-time as you edit.

  3. Iterate and Refine: Modify the generated .mmd file directly, or ask DinoAI to make specific changes.

Example:

Reusable GitGraph prompts for you and your team

You can create custom, standardized .dinoprompts for Mermaid's GitGraff Diagrams that ensure consistency across your data team. See step-by-step guide.


Core Git Operations

Basic Commands

  • commit: Add a new commit to current branch

  • branch: Create and switch to a new branch

  • checkout: Switch to an existing branch

  • merge: Merge a branch into current branch

Commit Customization

Branch Management

Common Data Team Workflows

Feature Development

Release Process

Hotfix Workflow

Advanced Features

Custom Commit Types

  1. NORMAL: Standard commit (default)

  2. REVERSE: Reverted commits

  3. HIGHLIGHT: Important commits

Cherry-picking

Orientation Options

  • Left to Right (default): gitGraph LR:

  • Top to Bottom: gitGraph TB:

  • Bottom to Top: gitGraph BT:

Configuration Options

Visual Customization

Branch Ordering

  • Set main branch order: mainBranchOrder

  • Custom branch order: branch develop order: 2

  • Default ordering follows appearance in code

Best Practices

  1. Use meaningful commit IDs and tags

  2. Group related changes in feature branches

  3. Mark significant releases with tags

  4. Highlight important commits

  5. Maintain clear branch naming conventions

  6. Document merge strategies

Common Use Cases

  • Feature branch workflows

  • Release management

  • Hotfix procedures

  • Data pipeline versioning

  • Model deployment strategies

  • Team collaboration patterns


Additional Resources

For more syntax options and advanced features, visit the official Mermaid documentation

Last updated

Was this helpful?