community.vyos.net.git/.github/workflows, branch feature/T9082-codeql-onboardVyOS community website (mirror of https://github.com/vyos/community.vyos.net.git)
https://git.amelek.net/vyos/community.vyos.net.git/atom?h=feature%2FT9082-codeql-onboard2026-07-14T12:17:57+00:00ci: T9082: onboard CodeQL scanning via central reusable workflow2026-07-14T12:17:57+00:00Yuriy Andamasovyuriy@vyos.io2026-07-14T12:17:57+00:00urn:sha1:5dd68988cc1244e9ad049afd401266d421e42b14
🤖 Generated by [robots](https://vyos.io)
T8943: ci: remove dead amplify branch from CI push trigger (#61)2026-06-02T19:00:47+00:00Yuriy Andamasovyuriy@vyos.io2026-06-02T19:00:47+00:00urn:sha1:7ade819ae7ed28a45c5b44bef7e386e19f02dfc2
The amplify branch no longer exists in this repo; the trigger entry is
unreachable. main was already retargeted to development in #59 (rollout 1c).
This completes the trigger cleanup so the list matches real branches.
🤖 Generated by [robots](https://vyos.io)ci: T8947: point CLA check at vyos-cla-signatures@production (rollout 1c follow-up) (#60)2026-05-31T08:17:10+00:00Yuriy Andamasovyuriy@vyos.io2026-05-31T08:17:10+00:00urn:sha1:b09621d62d2c8babdef66e9ab756f1577c24edf0
Rollout 1c (IS-503) renamed vyos-cla-signatures' default branch to `production`,
but cla-check.yml still called the reusable at @current. The `current` branch of
vyos-cla-signatures has diverged from `production` and its copy of cla-reusable.yml
writes signatures to `branch: 'current'` — so CLA signatures from this repo's PRs
were landing on the stale `current` branch instead of `production`.
Flip the ref to @production (whose cla-reusable.yml writes to `branch: 'production'`).
Note: migrating/reconciling signatures already accumulated on
vyos-cla-signatures@current (and whether to delete that branch) is a separate
operator decision tracked in IS-504 / T8947.
🤖 Generated by [robots](https://vyos.io)ci: T8943: retarget main.yml push trigger main->development (rollout 1c) (#59)2026-05-30T16:35:48+00:00Yuriy Andamasovyuriy@vyos.io2026-05-30T16:35:48+00:00urn:sha1:140ff43e6cbd59b01f2102baccac705794665dbd
The default-branch reorg renamed main->development (production is now the
default). main.yml deploys by mirroring github.ref_name to an AWS Amplify
branch, so the dead main trigger is replaced with development. The Amplify
app has a matching development branch (operator-confirmed). amplify/production
trigger entries left unchanged.
Tracking: T8943Merge branch 'main' into production2026-02-17T17:56:58+00:00Daniil Baturindaniil@baturin.org2026-02-17T17:56:58+00:00urn:sha1:637ead2e03d0d9957119dbe5c1cdceccaba04efbT7579: fix of the run trigger for CLA2025-07-14T10:52:29+00:00Yevhen Bondarenkoevgeniy.bondarenko@sentrium.io2025-07-14T10:52:29+00:00urn:sha1:8523d727fc9cbfcfaa4f2c106e3bb90868b1d052T7579: added workflow for CLA2025-07-04T12:44:35+00:00lemeshovich17667824+lemeshovich@users.noreply.github.com2025-07-04T12:44:35+00:00urn:sha1:1de2adb8eac51f70a7529689e27338638458a81dMerge branch 'main' into production2024-12-30T13:38:34+00:00Daniil Baturindaniil@baturin.org2024-12-30T13:38:34+00:00urn:sha1:ab710cf86aed004aadce092b475502a773587595fixed access to variables [no ci]2024-11-05T11:53:20+00:00Yevhen Bondarenkoevgeniy.bondarenko@sentrium.io2024-11-05T11:53:20+00:00urn:sha1:3ef6f5475300e78fda6f064f3aa2e8e05860afb1ci: fixed variable access issue2024-11-05T11:36:43+00:00Yevhen Bondarenkoevgeniy.bondarenko@sentrium.io2024-11-05T11:36:43+00:00urn:sha1:2129ca7ed105e4f0d24e3b1c081a7687e99258ec