-
Notifications
You must be signed in to change notification settings - Fork 20
chore: onboard onto unified pipeline #13
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
Conversation
|
I noticed CI wasn't running on here, so I added a GitHub Action. Let me know if I should be using Azure DevOps for CI as well. |
deepak1556
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, please use Azure pipelines for the PR runs as well.
9e6f734 to
ba721d0
Compare
|
Oh looks like the pipelines haven't been triggered. |
|
When I tried creating a new pipeline for this repo in Azure DevOps, I was prompted to select the azure-pipelines.yml file. I think this change might need to be merged into the main branch before Azure DevOps can set up the pipeline on its end. Here is the pipeline for the main branch file for reference, but this PR is getting rid of that file so it shouldn't be run. |
|
You can trigger a run from the branch based on the new pipeline path, triggered at https://dev.azure.com/monacotools/Monaco/_build/results?buildId=205459&view=results |
Ref https://github.com/microsoft/vscode-internalbacklog/issues/3191