/azp run

/azp run azure-pipelines-pullrequests

/azp run

/azp run

/azp run

/azp help run

/azp run fluentmigrator CI for PRs

/azp run fluentmigrator CI for PRs

/azp run "fluentmigrator CI for PRs"

@PhenX I still can't figure out why Azure Pipelines is not automatically triggering CI builds. I believe it broke when I renamed master to main, but can't prove it. I've been manually triggering them which is super tedious and time consuming for an open source project. I asked Andrew Arnott if he had any ideas. Additionally, I just tried removing branch protection from the main branch to see if that helps.

Well, that is weird. I renamed the pipeline and the check does not show up in AZP. My takeaway is AZP does not do well with renames in general because it relies on names rather than persistent identifiers (as a general observation). Git branches are not really persistent identifiers, either, as it is just listed in .git/refs/heads via the branch name and the sha1 commit hash.

@jayharris Sorry for taking so long to merge this. I really need to sort out the administrative side of Azure Pipelines, as it is a time sink manually triggering pipelines. I'll try to publish the release of 7.2.0 today.

@jzabroski would you consider migrating to GitHub actions ?

yeah I thought about asking Claude to port the yaml

@jzabroski If Claude or Copilot (I have it) does not do the trick maybe you could tryhttps://pipelinestoactions.azurewebsites.net/

I'll try it on my fork first. Thanks. Did not know about that website. Neat.

@jzabroski If Claude or Copilot (I have it) does not do the trick maybe you could tryhttps://pipelinestoactions.azurewebsites.net/

@PhenX It's a bit buggy but it mostly works - got me far enough where I was able to guess at the rest. Could you try taking what I have and seeing if you can get TestContainers to run as part of the build on GitHub Actions?https://github.com/jzabroski/fluentmigrator/pull/1/checks