Frontend
a11y-0.0.1
a11y-0.0.11.0.0
a11y-0.0.1
a11y-0.0.11.0.0
  • Introduction
  • Project Guidelines
    • INTRODUCTION
    • PROJECT SETUP
      • Project starter
      • Static type checking
      • Code Quality Tools
      • Enforcing good practices
      • Testing
      • Code versioning flow
      • Continuous Integration & Delivery
      • Isolated component development
    • EFFECTIVE AND CONSISTENT WORKFLOW
      • Code structure, architecture
      • Code versioning and review flow
      • Testing
      • Static type checking
      • Continuous Integration & Delivery
      • Dependency checking
      • Project Management Tools
      • Communication
    • THE QUALITY OUTPUT
      • Great UX/UI
        • User Experience
        • Responsive Web Design
        • SEO, SMO
        • Progressive Web Apps
      • Stability
        • Documentation
        • Analytics & Error Tracking
        • Quality Assurance
      • Performance
        • Bunde Size
        • Deployment
        • Audits & Reports
      • Security
      • Accessibility
        • Why a11y?
        • Fundamentals
        • User stories
        • A11y tools
        • Checklist
    • FINAL WORDS
Powered by GitBook
On this page

Was this helpful?

  1. Project Guidelines
  2. PROJECT SETUP

Code versioning flow

PreviousTestingNextContinuous Integration & Delivery

Last updated 5 years ago

Was this helpful?

Good git practices, meaningful commit messages, branch strategies, pull request templates. All of these improve efficiency and consistency. And it’s all very helpful for onboarding.

Community standard is a git-flow which is embracing doing a semantic release. We recommend using it on larger projects.

But overall and use . They will help to establish a nice and easy way of following commit history.

Code quality tools
be a good “commitzen”