| 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 the VyOS-Networks twin) for the public
vyos/.github force_workspace reusable. Inert on this public source (owner
guard); active on the mirror. force_workspace_enabled per-consumer (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)
|
|
Mirror Pipeline Rollout 2 Task 6. Uniform canonical wrapper:
trigger branches [rolling, production], permissions: contents: read,
drop redundant wrapper-level MIRROR_ENABLED guard (now central).
🤖 Generated by [robots](https://vyos.io)
|
|
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
|
|
(#102)
Replaces the legacy PAT-based caller with the uniform App-ready stub.
Switches to `secrets: inherit` and `vars.MIRROR_ENABLED` opt-out guard.
Plan: ~/.claude/plans/2026-05-26-mirror-rollout-1b-revised.md Task 5
🤖 Generated by [robots](https://vyos.io)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Because they don't have the permissions to do it. Instead, reword the
message to ask people to ping mitechie, in line with the rest of the
message.
|
|
This reverts commits fad919aa2c894abaa3af88aed1e064c1220937fe ("stale:
disable check for holiday break (#735)") and
e4f2d6139a802e659c571f581763eddeee715e2f ("stale: fix error in
definition (#740)").
|
|
This should fix the error, and also allows us to manually trigger the
workflow.
|
|
We're unlikely to see any activity on many PRs over the next couple of
weeks, so don't close out inactive PRs for the duration.
|
|
We missed this one when we updated all the docs for the Canonical team's
management change.
|
|
This workflow will label pull requests with "stale-pr" if they haven't
seen activity for 14 days. It will then close them out after a further
7 days of inactivity.
|
|
The list so far is partial.
|
|
Instead of using the username that triggered the action (which, in the
case of a committer merging master into a PR branch will be the
committer), always use the username of the submitter of the pull
request.
|
|
Github api doesn't allow read-write access to labels or comments when
running from a pull_request fork during CI.
This restriction results in an API error
message: "Resource not accessible by integration"
If we want to run this action per pull_request, we need to convert the
action to fail the PR status check and emit the required steps to sign the
CLA to the console on the PR's failed status tab.
|
|
Check whether the pull request submitter has signed the CLA due
to presence of github.actor in tools/.lp-to-git-user
Set 'CLA signed' if present, 'CLA not signed' label if absent
* grep for the full github username in CLA file
Co-authored-by: Daniel Watkins <daniel@daniel-watkins.co.uk>
|
