You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I create a new repository via a script using a template repository. The template repository has AL-Go set up.
The issue I'm facing is that when creating a new repository (from a template) the initial commit starts a CI/CD -pipeline.
This is very much unnecessary, it's a template repository, and the validations have been run when stuff's been merged to main. And now this pipeline gets run every single time a new repo is created from the template.
Best way to skip this Initial commit CI/CD?
The text was updated successfully, but these errors were encountered:
You could cancel it through your script with GH Cli. Something like this: gh run list --json databaseId --status in_progress | ConvertFrom-Json | ForEach-Object { gh run cancel $_.databaseId }
Not sure if we can do anything from AL-Go to prevent this. CI/CD runs on push by default in AL-Go.
Yeah, the initial commit is annoying - but it isn't one we control - GitHub kicks that one off.
Maybe we can make it faster at determining that there is nothing to build.
I created an organizational webhook that calls an azure function for every workflow. This azure function cancels the workflows if the payload ["workflow_run"]["display_title"] contains "Initial commit", using an http request to github's api. Not super elegant, works.
Question
Hi,
I create a new repository via a script using a template repository. The template repository has AL-Go set up.
The issue I'm facing is that when creating a new repository (from a template) the initial commit starts a CI/CD -pipeline.
This is very much unnecessary, it's a template repository, and the validations have been run when stuff's been merged to main. And now this pipeline gets run every single time a new repo is created from the template.
Best way to skip this Initial commit CI/CD?
The text was updated successfully, but these errors were encountered: