From 4c49149ea6fb29dad17dc333e05d5c10e1f1d269 Mon Sep 17 00:00:00 2001 From: Stamen Stoychev Date: Fri, 30 Oct 2026 11:45:24 +0200 Subject: [PATCH] docs(agents): add GitHub Actions workflow guidance Pin actions to commit SHAs, use the current create-github-app-token inputs (client-id) instead of copying older workflows, dispatch deploys to IgniteUI/igniteui-actions and validate workflows with actionlint. Co-Authored-By: Claude Opus 5.5 --- AGENTS.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 7a00590f79f..da02596012a 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -87,6 +87,13 @@ css-naming-convention.md ← CSS naming rules - Before introducing a breaking rename/removal without a migration plan. - Before creating a migration schematic — confirm the change is truly breaking. +### GitHub Actions workflows + +- Pin every action and reusable workflow to a full commit SHA with a `# vX.Y.Z` comment. +- Use each action's current inputs instead of copying older workflows. For example, `actions/create-github-app-token` takes `client-id: ${{ secrets.IGNITEUI_GITHUB_APP_CLIENT_ID }}`; `app-id` is deprecated since v3.1.0. +- Deploys to Infragistics infrastructure go through a `repository_dispatch` to `IgniteUI/igniteui-actions`. +- Validate changed workflows with `actionlint`. + ## Commands | Action | Command |