Repository navigation
Include agentic workflows when updating system files from AL-Go or indirect templates - #2409
Freddy Kristiansen (freddydk) wants to merge 5 commits into
Conversation
|
Freddy Kristiansen (@freddydk) please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
|
@microsoft-github-policy-service agree |
There was a problem hiding this comment.
🟡 Changes recommended
Regression coverage is needed for Markdown workflow inclusion through direct and indirect templates and explicit exclusions.
1 open issue
What changed in this PR
Extends AL-Go system-file updates to include agentic workflow definitions from direct and indirect templates.
Changes:
- Includes
.github/workflows/*.mdfiles asagentic workflowfiles. - Documents the behavior in release notes.
| File | Description |
|---|---|
| RELEASENOTES.md | Announces inclusion of agentic workflow definitions. |
| Actions/CheckForUpdates/CheckForUpdates.HelperFunctions.ps1 | Adds workflow Markdown files to default inclusion rules. |
Review effort: Balanced
|
@microsoft-github-policy-service agree |

This pull request updates the handling of system files to ensure that agentic workflows are included when updating from AL-Go or indirect templates. It adds support for
.mdfiles in the.github/workflowsdirectory, which is the recommended location for agentic workflows.Support for agentic workflows:
CheckForUpdates.HelperFunctions.ps1: TheGetDefaultFilesToIncludefunction now includes.mdfiles from.github/workflows, classifying them asagentic workflowfiles.Documentation:
RELEASENOTES.md: Added a note explaining that.mdfiles in.github/workflowsare now included when updating system files, supporting the recommended practice for agentic workflows.