Skip to content

Docs: add suggested git-workflow conventions in GIT_WORKFLOW.md#1365

Merged
gusthoff merged 2 commits into
AdaCore:mainfrom
gusthoff:dev/topic/infrastructure/docs/branch-commit-conventions/2026-06-05
Jun 5, 2026
Merged

Docs: add suggested git-workflow conventions in GIT_WORKFLOW.md#1365
gusthoff merged 2 commits into
AdaCore:mainfrom
gusthoff:dev/topic/infrastructure/docs/branch-commit-conventions/2026-06-05

Conversation

@gusthoff
Copy link
Copy Markdown
Collaborator

@gusthoff gusthoff commented Jun 5, 2026

No description provided.

gusthoff and others added 2 commits June 5, 2026 20:39
Document the suggested git workflow for the project in a dedicated
GIT_WORKFLOW.md (kept out of CONTRIBUTING.md, since it is not crucial for
content contributors), and link to it from CONTRIBUTING.md:

- Topic-branch naming: the dev/issue/<ticket>/... and dev/topic/<area>/...
  forms, the content vs infrastructure split for the learning material, the
  <descriptor> slug, the optional trailing YYYY-MM-DD date, and the suggested
  main + feature-branch approach (merged --no-ff) for bigger implementations.
- Canonical commit-message tags: "<Tag>: <imperative>" with a colon (not
  brackets), content tags naming the nature of the change and infrastructure
  tags naming the component touched, with issue references in the body.

These are presented as suggested (non-mandatory) recommendations. Validation:
documentation-only change; rendered Markdown reviewed for correct structure.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@gusthoff gusthoff merged commit d88fca5 into AdaCore:main Jun 5, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant