Create Empty build-release.yml#26
Merged
Merged
Conversation
jamesadevine
approved these changes
Jan 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There are a couple of restrictions in the ADO UI on creating a pipeline to a GitHub repository. The main issue is the yaml file you link to needs to be in the default branch (aka Main). The branch used in the pipeline can be changed after pipeline creation, but the location in the branch and yaml file name can't. So basically, there needs to be a
build-release.ymlin the.azuredevopsfolder in themainbranch. This file is nothing other than a place holder file -- but it needs to exist to create the pipeline correctly initially.This other PR https://github.com/Azure/azure-sphere-tools/pull/25/changes which should get merged after, has the actual
build-release.ymlpipeline definition.