We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
While reviewing #36431 where only .md were edited, I've noticed that the CI was triggered and all tests executed:
.md
We had a similar problem in the performance repo in the past which was solved by: dotnet/performance#355
I am an AzDO n00b and I could not find azure-pipelines.yml in this repo, so this is why I create an issue instead of sending a PR.
azure-pipelines.yml
/cc @ViktorHofer
The text was updated successfully, but these errors were encountered:
Tagging subscribers to this area: @safern, @ViktorHofer Notify danmosemsft if you want to be subscribed.
Sorry, something went wrong.
@adamsitnik seems like we can't easily ignore all .MD files. I think there's a uservoice ticket somewhere against AzDO to support that.
Moving to future, let's see if Github actions will allow this.
Closing as not actionable (AzDO limitation). Feel free to reopen when we moved off AzDO.
Successfully merging a pull request may close this issue.
While reviewing #36431 where only
.md
were edited, I've noticed that the CI was triggered and all tests executed:We had a similar problem in the performance repo in the past which was solved by: dotnet/performance#355
I am an AzDO n00b and I could not find
azure-pipelines.yml
in this repo, so this is why I create an issue instead of sending a PR./cc @ViktorHofer
The text was updated successfully, but these errors were encountered: