Frontend
CtrlK
1.0.0
1.0.0
  • Introduction
  • Project Guidelines
    • INTRODUCTION
    • PROJECT SETUP
      • Frameworks
      • 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
      • Continuous Integration & Delivery
      • Dependency checking
      • Project Management Tools
      • Communication
    • THE QUALITY OUTPUT
      • Great UX/UI
        • Design & User Experience
        • SEO, SMO
      • Accessibility
        • Introduction
        • Why a11y?
        • Fundamentals
        • A11y in STRV
          • Share Knowledge
          • Project Life Cycle
          • A11y culture
      • Performance
        • Bundle Size
        • Deployment
        • Audits & Reports
      • Stability
        • Documentation
        • Analytics & Error Tracking
        • Quality Assurance
      • Security
    • FINAL WORDS
    • ACKNOWLEDGEMENT
Powered by GitBook
On this page

Was this helpful?

  1. Project Guidelines
  2. PROJECT SETUP

Code versioning flow

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 be a good “commitzen” and use Code quality tools. They will help to establish a nice and easy way of following commit history.

PreviousTestingNextContinuous Integration & Delivery

Last updated 5 years ago

Was this helpful?