Repository navigation
Support .lock.yaml files #21828
Description
Activity
- locked and limited conversation to collaborators
on Mar 19, 2026 - unlocked this conversation
on Mar 19, 2026 - linked a pull request that will close this issueSupport .lock.yaml files as compiled workflow output #22030
on Mar 20, 2026 How critical is this?
It’s nice to have, but not critical.
- locked and limited conversation to collaborators
on Mar 20, 2026 - unlocked this conversation
on Mar 20, 2026 This change would introduce e significant a bit of burden.
Could you elaborate?
- locked and limited conversation to collaborators
on Mar 25, 2026 - unlocked this conversation
on Mar 25, 2026
Right now,
workflow.mdgets compiled toworkflow.lock.yml. If the file is renamed toworkflow.lock.yaml, runninggh aw compilecreates a newworkflow.lock.ymlinstead of updating the existingworkflow.lock.yaml.Expected Behavior
If
workflow.lock.yamlexists,gh aw compileshould update it instead of generatingworkflow.lock.yml.Rationale
Even though
.ymlis the default file extension for workflow files, GitHub supports.yamlfiles in.github/workflows(like here), providing consistency for repositories where.yamlis the established pattern. This includes support fordependabot.yamlandaction.yamlin workflow action repositories (living proof).