New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make TypeMap Injectable #1755 #1757
Conversation
Fix "master" branch references to be "main"
I've submitted a community support request here: https://github.com/orgs/community/discussions/114175 |
If I can't get this working, I may pivot to using GitHub Actions to directly trigger the Azure DevOps Pipeline: https://learn.microsoft.com/en-us/azure/devops/release-notes/2019/sprint-161-update It's not clear to me that will actually work, but it's something. @eloekset Any thoughts on this approach? "Gross", maybe? :) @schambers If you could pull down this PR and tell me if all the tests pass on your machine, that would be helpful, too... |
I'm not sure what has happened, but it looks like it doesn't help triggering the build manually. I triggered it on the main branch referring to the latest commit of this PR, and the checks ran successfully, but the status is not reported back here, so I guess we'll just have to merge the PR without waiting for the requirements to be met. https://dev.azure.com/fluentmigrator/fluentmigrator/_build/results?buildId=856&view=results |
How did you trigger it manually? I couldnt see how to trigger a specific commit through the UI. |
@eloekset Actually, what you did worked - see this screenshot. But the overall PR status is still gated because not all commits in the chain got "built" even if they one is a no-op (fast forward merge) and the other is updating the README.md (which I did as an attempt to see if that would force the process to heal itself + finally fix at README file). |
@eloekset Thanks, It didn't occur to me that conceptually a PR commit was part of the main branch. |
Fixes #1063, #1724 and #1618.
Possible breaking changes include:
ColumnBase
now raises an obsolete warning: "Use ColumnBase instead. Going forward, column models must have a db-specific type map model."