Etendo Git Workflow Conventions

To enforce Git branch naming conventions for Etendo ERP projects, apply predefined patterns like feature/{JIRA-KEY} or hotfix/#{GH}-{JIRA-KEY} to maintain code integrity across the development team.

The correct commit message format for Etendo Git workflows requires specific prefixes and character limits, such as formatting subsequent commits with Feature ETP-1234: to ensure consistency and improve code review efficiency.

Standardizing branch naming helps with Git code reviews by preventing inconsistencies across the development team. Adherence to predefined patterns for features and hotfixes facilitates automated checks and improves review efficiency.

You need to use a hotfix branch pattern in Git when addressing urgent issues in Etendo ERP projects. This requires adherence to the predefined hotfix/#{GH}-{JIRA-KEY} format to maintain code integrity and facilitate automated checks.

No, you cannot use custom commit prefixes outside the Etendo Git standards. This Skill ensures all Git operations adhere to established commit message conventions, requiring specific fields and prefixes to maintain consistency.

Yes, the Etendo Git workflow supports automated checks for branch patterns. Enforcing predefined patterns for features, hotfixes, and epics facilitates automated checks and maintains code integrity across the development team.