[Bug]: CICD runs after every commit by 'Update AL-Go System Files'
Open
Beginner friendly
Nobody has claimed this yet.
bug
- Dominant language
- PowerShell
- Stars
- 506
- Forks
- 203
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 6
Description
AL-Go version
v9.2
Describe the issue
The commit created by 'Update AL-Go System Files' always includes .github/AL-Go-Settings.json with a changed templateSha.
CICD runs, even though logically it doesn't need to.
name: ' CI/CD'
on:
workflow_dispatch:
push:
paths-ignore:
- '**.md'
- '.github/workflows/*.yaml'
- '!.github/workflows/CICD.yaml'
...
Expected behavior
CICD should not run, when 'Update AL-Go System Files' only updates templateSha in .github/AL-Go-Settings.json.
Steps to reproduce
- push empy commit to Template repo
- run 'Update AL-Go System Files' on App repo
Additional context (logs, screenshots, etc.)
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with .github/workflows/CICD.yaml and .github/AL-Go-Settings.json, then reproduce the documented flow by pushing an empty commit to the Template repo and running Update AL-Go System Files on an App repo. Done means a commit that only changes templateSha does not trigger the CI/CD workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, powershell
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 74/100