𝗔 𝗣𝗥𝗔𝗚𝗠𝗔𝗧𝗜𝗖 𝗚𝗜𝗧 𝗪𝗢𝗥𝗞𝗙𝗟𝗢𝗪 𝗙𝗢𝗥 𝗖𝗥𝗢𝗦𝗦 𝗥𝗘𝗣𝗢𝗦𝗜𝗧𝗢𝗥𝗬 𝗖𝗢𝗟𝗟𝗔𝗕𝗢𝗥𝗔𝗧𝗜𝗢𝗡

𝗔 𝗣𝗥𝗔𝗚𝗠𝗔𝗧𝗜𝗖 𝗚𝗜𝗧 𝗪𝗢𝗥𝗞𝗙𝗟𝗢𝗪 𝗙𝗢𝗥 𝗖𝗥𝗢𝗦𝗦 𝗥𝗘𝗣𝗢𝗦𝗜𝗧𝗢𝗥𝗬 𝗖𝗢𝗟𝗟𝗔𝗕𝗢𝗥𝗔𝗧𝗜𝗢𝗡

You manage multiple repositories. You need a system to keep code safe. This workflow helps your team stay aligned.

Set a shared model first.

• main for stable releases.
• develop for integration.
• feature/ for new work.
• hotfix/ for urgent fixes.

Handle cross-repo work with a coordination pattern.

• Create one Epic ID.
• Use this ID in every branch name.
• Link PRs across all repositories.
• Reference the Epic in every PR.

Follow these rules for clean history.

• Never commit to main or develop.
• Use small commits.
• Limit one logical change per commit.

Automate boring tasks.

• Use pre-commit hooks for linting.
• Use pre-push hooks for tests.
• Update changelogs automatically.

Release with care.

• Use a shared version scheme.
• Link all related changes in one release note.
• Have a rollback plan ready.

Keep it light.

• Do not force complex PRs.
• Document dependencies.
• Assign one owner for coordination.

Source: https://dev.to/therizwansaleem/a-pragmatic-git-workflow-for-cross-repository-collaboration-m1g