| name | vionix-development |
| description | Development rules for the Vionix DevSecOps platform repositories (vionix-github-workflows, github/vionix-lookinglass, vionix-devsecops-apps): PR conventions (Jira/PRD title prefixes; labels, project, and assignee required on agentic PR creation), the GitHub rule that workflow_dispatch workflows MUST be merged to the default branch before they can be triggered, and how to land stacked PRs through the merge queue. Use this skill whenever creating branches or PRs agentically, introducing or testing a workflow_dispatch/schedule workflow, or merging PRs in these repositories.
|
Vionix Development Rules
workflow_dispatch requires the DEFAULT branch
A workflow with a workflow_dispatch (manual) trigger can only be dispatched once the workflow
file exists on the default branch (main). This is a GitHub platform behavior, not ours:
"This event will only trigger a workflow run if the workflow file is on the default branch."
— GitHub Docs: Events that trigger workflows — workflow_dispatch
Rules that follow from it:
- PRs introducing a
workflow_dispatch (or schedule) workflow MUST be merged to the default
branch before the trigger can be used — plan the try-out AFTER the merge, not from the PR
branch.
- Prefer landing such PRs through the merge queue (below) so the experiment starts from a
clean, serialized
main.
PR conventions
- Title prefix: every PR title MUST be prefixed by the Jira ticket (e.g.
:octocat: :bug: fix the sync race). A PRD prefix is acceptable too for the
LookinGlass feature PRDs (e.g. :octocat: :sparkles: usecase replacement PRs).
- Agentic PR creation — when a PR is created the agentic way, ALWAYS set on creation:
- Labels: pick the appropriate existing label(s) (e.g.
enhancement, bug,
documentation);
- Project: associate the repo/product project (for
github/vionix-lookinglass: the
org project Github Actions Mirror Requests);
- Assignee: assign the current user — whoever holds write permission and is making the
change (e.g.
gh pr edit N --add-assignee @me);
- Keep the
Co-Authored-By: Oz <oz-agent@warp.dev> attribution in commits and PR bodies.
- Branches: GitFlow topic branches (
feature/..., bugfix/...). For stacked work, branch
002 from the 001 branch; retarget both PRs to main when landing through the merge queue.
Merge queue
main of github/vionix-lookinglass is governed by the ruleset
"main merge queue (PRD experiment)" (merge method: merge; grouping: ALLGREEN).- Queue page: <https:///github/vionix-lookinglass/queue/main>
- To land a PR: use "Merge when ready" on the PR — GitHub adds it to the queue, builds the
temporary
gh-readonly-queue/* group branches, and merges in order.
- Stacked PRs: queue them in stack order (001 before 002). The later branch contains the
earlier commits, so queueing the tip first would land everything at once and leave the
earlier PR empty.
- Merge queue on GHES requires the ruleset/branch protection on the target branch (available on
our GHES 3.19); it does not orchestrate PRs whose base is another feature branch.
