| Age | Commit message (Collapse) | Author |
|
|
|
(#235)
Switches from explicit PAT/REMOTE_OWNER secrets pass-through to
secrets: inherit and adopts the uniform stub with vars.MIRROR_ENABLED
per-repo kill-switch. Behavior-neutral against current central workflow.
Plan: ~/.claude/plans/2026-05-26-mirror-rollout-1b-revised.md Task 5
🤖 Generated by [robots](https://vyos.io)
|
|
* T8615: add Mergify config (extends: mergify central template)
Adds the org-local central-config inheritance file per the T8615 sweep
(re-scoped 2026-05-28). 4-line minimum: extends: mergify resolves to
vyos/mergify which provides commands_restrictions (9 slash commands x
4-sender allowlist), conflict labeler, PR-title T-ID format check,
opt-in auto-update, and the backport-conflict merge protection.
merge_protections_settings: reporting_method: check-runs declared
explicitly per-repo because only defaults and commands_restrictions are
documented as merging across extends: -- pin to current behavior pre
the 2026-07-31 default flip per data/github.md Mergify gotchas table.
Phase 0 CR: 0 finding(s). Known false positive: CR flags
extends: mergify as 'not a documented built-in preset' but Mergify
documents the org-local form at https://docs.mergify.com/configuration/sharing/.
Refs: T8615 (re-scoped 2026-05-28), IS-421
Generated by robots https://vyos.io
* T8615: switch yaml-language-server schema URL to JSON-schema
Replaces the human-docs file-format URL (which serves HTML and cannot
drive editor validation) with the machine-readable JSON-schema URL
that yaml-language-server actually resolves for autocomplete and
schema validation.
Old: https://docs.mergify.com/configuration/file-format/
New: https://docs.mergify.com/mergify-configuration-schema.json
Phase 0 CR: 0 finding(s).
Refs: T8615 (re-scoped 2026-05-28), IS-421
Generated by robots https://vyos.io
|
|
coderabbit: T8851: add .coderabbit.yaml for central-config inheritance
|
|
|
|
T8835: added pr mirror workflow
|
|
|
|
general: T8595: add AGENTS.md
|
|
|
|
|
|
|
|
CI: T7579: fix of the run trigger for CLA
|
|
|
|
T7579: added workflow for CLA
|
|
|
|
|
|
T6524: remove vyatta-interfaces.pl, no longer required
|
|
|
|
Github: PR Template: make related tasks optional
|
|
|
|
|
|
|
|
T5826: debian: add dmidecode as an explict depdency
|
|
On non-x86 systems, dmidecode may not be specified as an explicit
dependency of the packages that recommend it (like laptop-detect and virt-what).
Ensure it is installed regardless of target architecture.
|
|
image: T4516: remove standalone_root_pw_reset, now in vyos-1x
|
|
|
|
remote: T5726: Replace the download procedure call
|
|
|
|
boot: T5739: Fixed password recovery
|
|
This change fixes a filter used for `sed` during password reset in the
`set_encrypted_password()` function.
Old logic: search between `user username {` and the first line with `}` does not
work for users with extra options in config, like public keys.
New logic: search between `user username {` and the first line with
`encrypted-password` which should cover all possible combinations, except
situations when a password is not presented in a configuration file.
|
|
T4320: remove legacy version files
|
|
Component version data now resides in vyos-1x XML.
|
|
dns: T5144: Apply migration for dynamic dns path update
|
|
installer: T4776: Fixed installation on NVME in RAID-1 mode
|
|
|
|
install: T5568: Determine user TTY when elevated by sudo
|
|
Also fix indentation
|
|
T5520: avoid cp from /config during update, after coreutils change
|
|
A change in behaviour of coreutils 'cp' reveals a problem when doing a
'cp -a' from the bind mount /config; use /opt/vyatta/etc/config instead.
|
|
This change fixes installation into two NVME devices. It should be considered as
a temporary solution before migration to the new installer.
|
|
T671: remove more dead scripts
|
|
|
|
T671: remove unused scripts
|
|
|
|
Commit f34e9028 ("T5136: properly unmount filesystems after installation") assumed
it would be a good idea to simply rm -rf the new root folder. This could have
a bad, non booting side effect.
Warn user if unmount fails but the filesystem is synced anyway. The rest is
handled by the Kernel on reboot.
|
|
|
|
|
|
|
|
|
|
|