| Age | Commit message (Collapse) | Author |
|---|
|
Mergify ignore_conflicts:true already creates the backport workspace PR +
resolves toward theirs + applies backport-conflict for path-drift conflicts
(verified by canary VyOS-Networks/ipaddrcheck#26/#27). force_workspace's
'No backport have been created' trigger never fires under that config.
T8943 / IS-510.
|
|
Source-side wrapper (mirrored to VyOS-Networks/ipaddrcheck) that triggers the
public vyos/.github force_workspace reusable on Mergify backport-conflict
comments. Inert on this public source (owner guard); active on the mirrored
target. force_workspace_enabled is per-consumer (consumers.yaml), default false.
🤖 Generated by [robots](https://vyos.io)
|
|
Adds the source-side LTS-name advisory caller (mirror-pipeline). Non-blocking;
posts a generic advisory if a PR title/body references a release-train branch name.
🤖 Generated by [robots](https://vyos.io)
|
|
Per Mirror Pipeline Redesign Rollout 2: standardize the wrapper to the
canonical stub. Inclusion + kill-switch logic moves into the central
workflow + consumers.yaml; this wrapper is now a thin pass-through.
Changes from post-1b wrapper:
- branches: [rolling] -> [rolling, production] (heterogeneous fleet)
- permissions: contents:write/pull-requests:write/issues:write ->
contents:read (no side effects in wrapper; central workflow holds
write perms via App tokens — see vyos/.github canonical stub
permissions fix vyos/.github#133)
- Remove 'vars.MIRROR_ENABLED != false' gate from wrapper if: clause
(kill-switch enforced in central workflow's check-consumer-inclusion
+ per-side-effect re-checks)
Spec: /Users/syncer/.claude/specs/2026-05-16-mirror-pipeline-redesign-design.md §4.2.3
Permissions fix spec: /Users/syncer/.claude/specs/2026-05-30-canonical-stub-permissions-fix-design.md
Plan: /Users/syncer/.claude/plans/2026-05-17-mirror-pipeline-rollout-2-inclusion-mechanism.md Task 6
Permissions fix plan: /Users/syncer/.claude/plans/2026-05-30-canonical-stub-permissions-fix.md
🤖 Generated by [robots](https://vyos.io)
|
|
PR #33 broke this consumer's mirror with startup_failure. Root cause:
GitHub's reusable-workflow permissions model. The canonical stub set
permissions: contents:read but the central reusable workflow declares
contents:write/pull-requests:write/issues:write at top level. Per docs:
'If you specify the access for any of these scopes at a level less
than the permissions defined by the called workflow, the entire
workflow will fail.'
Restoring the post-1b wrapper while we update the canonical stub
design (either drop central's top-level permissions block, or keep
write perms in the wrapper).
🤖 Generated by [robots](https://vyos.io)
|
|
Per Mirror Pipeline Redesign Rollout 2: standardize the wrapper to the
canonical stub. Inclusion + kill-switch logic moves into the central
workflow + consumers.yaml; this wrapper is now a thin pass-through.
Changes from post-1b wrapper:
- branches: [rolling] -> [rolling, production] (broaden trigger for
heterogeneous default-branch fleet; central + consumers.yaml gate the
actual mirror)
- permissions: contents:write/pull-requests:write/issues:write ->
contents:read (no side effects in wrapper; central workflow holds
write perms via App tokens)
- Remove 'vars.MIRROR_ENABLED != false' gate from wrapper if: clause
(kill-switch now enforced inside check-consumer-inclusion job +
per-side-effect re-checks in process-unmirrored-PR)
Spec: ~/.claude/specs/2026-05-16-mirror-pipeline-redesign-design.md §4.2.3
Plan: ~/.claude/plans/2026-05-17-mirror-pipeline-rollout-2-inclusion-mechanism.md Task 6
🤖 Generated by [robots](https://vyos.io)
|
|
Rollout 1c reference migration on vyos/ipaddrcheck prior to the default-
branch rename. Updates this repo's own trunk references current->rolling:
pr-mirror trigger branches, trigger-rebuild trigger branches (LTS entries
kept), and the AGENTS.md branch-model note. HIGH-producer pins were already
swept to @production in Task 2. Tracking: T8943
|
|
Rewrites uses: pins to the three HIGH-fanout producers (vyos/.github,
vyos/vyos-cla-signatures, VyOS-Networks/vyos-reusable-workflows) from their
old default branch to the new production compat branch staged in Task 1.
No functional change; pin-ref rewrite only.
Tracking: T8943
|
|
canary) (#30)
Switch from explicit `secrets: PAT/REMOTE_OWNER` pass-through to
`secrets: inherit`, and adopt the uniform stub shape. Behavior-neutral
against the current PAT-using central workflow (`inherit` populates
`PAT`/`REMOTE_OWNER` by name from org-level secrets); prepares for the
App-token central-workflow update (Task 7).
First (canary) consumer of the 25-repo Task 5 migration.
Plan: ~/.claude/plans/2026-05-26-mirror-rollout-1b-revised.md Task 5
|
|
|
|
policy update
|
|
|
|
|
|
|
