Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
branching-strategy - Skill - OpenSmartRoute
Skillv1.0.0
branching-strategy
Use this instruction when proposing, reviewing, or executing Git branching workflows for this repository.
Instruction file imported from LucasQuintela23/ticketing-platform (.github/instructions/branching-strategy.instructions.md). Copyright stays with the author.
Branching Strategy Rule
Mandatory branch roles:
main: production-ready history only.
staging: QA/UAT validation before production.
development: integration branch for active development.
Mandatory promotion order:
development -> staging
staging -> main
Mandatory hotfix rule:
Start hotfix from main.
Merge hotfix to main.
Back-merge the same change to staging and development.
Copilot must not suggest flows that bypass staging for standard releases.
For step-by-step release execution guidance, use the skill at:
Copy one of these into your project. Installing also returns the manifest and these snippets.
yaml
targets:
- https://api.opensmartroute.ai/api/v1/registry/lucasquintela23-ticketing-platform-branching-strategy-in-363276/manifest # or paste the manifest below
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
