We have a need to trigger new releases when a new branch is created in an Azure DevOps git repo. At the moment it looks like the VSTS/TFS plugin works for a static branch name. Is there a way to configure these triggers to recognize newly created branches on a repo?
All changes to B have already been validated by previous builds and weren’t changed in the last commit, so only A should fire.
Does this mean that the pipeline will be triggered if the branch contains a change to the matching path, regardless of whether the path was updated in the last commit? Not very convenient because you don’t want to rebuild the project from scratch when nothing has changed.