🪃
Engineering Playbook
  • Engineering Playbook
  • Agile Development
    • Kanban from the start
    • Daily Stand-up
    • Collaboration
      • Mobile Designer X Mobile Developer
    • Backlog Management
      • Backlog Refinement
    • Card Management
      • Epics
      • User story
        • Collaboration experience with acceptance criteria
        • Proper acceptance criteria
      • Task
      • Bug
      • Hotfix
      • Sub-task
      • Defect
      • Columns
      • Card organization
      • Column Limit
      • Board Templates
    • Pull System Task Assignment
    • Retrospectives
    • Team Agreement
      • Working Agreement
      • Definition of Ready
      • Definition of Done
    • Agile Metrics
  • Github
    • Source Control
    • Merge Strategies
    • Versioning
    • Code Reviews
      • Author's Checklist
      • Reviewer's Checklist
  • Documentation
    • GraphQL as an API Doc
  • DevOps
    • Continuous Integration
Powered by GitBook
On this page
  • 🥅 Goals
  • General Guidance
  • Create a new repository
  • Resources

Was this helpful?

  1. Github

Source Control

🥅 Goals

  • Following industry best practice to work

  • Improve code quality by enforcing reviews before

  • Improve traceability of features and fixes through a clean commit history.

General Guidance

Be consistent

Create a new repository

  • Agree on the branch, release, and merge strategy

  • Define the merge strategy

  • Lock the default branch and merge using pull request (PRs)

  • Establish branch/PR policies

  • For public repositories the default should contain the following files:

    • LICENSE

    • README.md

    • CONTRIBUTING.md

Resources

  1. https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit

  2. https://www.conventionalcommits.org/en/v1.0.0-beta.4/

PreviousAgile MetricsNextMerge Strategies

Last updated 3 years ago

Was this helpful?