[ci] fix path to branchClassification.yml#10519
Merged
jonathanpeppers merged 1 commit intomainfrom Sep 24, 2025
Merged
Conversation
When cherry-picking the commit, I noticed:
Updating 61674e1..e04201b
Fast-forward
.../policies/branchClassification.yml\342\200\216" | 13 +++++++++++++
1 file changed, 13 insertions(+)
create mode 100644 ".azuredevops/policies/branchClassification.yml\342\200\216"
`\342\200\216` indicated some weird invisible character!
I must have done this when copy-pasting the file path from GitHub's
web UI?
Rename the file to the correct name:
Changes to be committed:
renamed: ".azuredevops/policies/branchClassification.yml\342\200\216" -> .azuredevops/policies/branchClassification.yml
jonathanpeppers
added a commit
that referenced
this pull request
Sep 24, 2025
When cherry-picking the commit, I noticed:
Updating 61674e1..e04201b
Fast-forward
.../policies/branchClassification.yml\342\200\216" | 13 +++++++++++++
1 file changed, 13 insertions(+)
create mode 100644 ".azuredevops/policies/branchClassification.yml\342\200\216"
`\342\200\216` indicated some weird invisible character!
I must have done this when copy-pasting the file path from GitHub's
web UI?
Rename the file to the correct name:
Changes to be committed:
renamed: ".azuredevops/policies/branchClassification.yml\342\200\216" -> .azuredevops/policies/branchClassification.yml
jonathanpeppers
added a commit
that referenced
this pull request
Sep 24, 2025
When cherry-picking the commit, I noticed:
Updating 61674e1..e04201b
Fast-forward
.../policies/branchClassification.yml\342\200\216" | 13 +++++++++++++
1 file changed, 13 insertions(+)
create mode 100644 ".azuredevops/policies/branchClassification.yml\342\200\216"
`\342\200\216` indicated some weird invisible character!
I must have done this when copy-pasting the file path from GitHub's
web UI?
Rename the file to the correct name:
Changes to be committed:
renamed: ".azuredevops/policies/branchClassification.yml\342\200\216" -> .azuredevops/policies/branchClassification.yml
jonathanpeppers
added a commit
that referenced
this pull request
Sep 25, 2025
When cherry-picking the commit, I noticed:
Updating 61674e1..e04201b
Fast-forward
.../policies/branchClassification.yml\342\200\216" | 13 +++++++++++++
1 file changed, 13 insertions(+)
create mode 100644 ".azuredevops/policies/branchClassification.yml\342\200\216"
`\342\200\216` indicated some weird invisible character!
I must have done this when copy-pasting the file path from GitHub's
web UI?
Rename the file to the correct name:
Changes to be committed:
renamed: ".azuredevops/policies/branchClassification.yml\342\200\216" -> .azuredevops/policies/branchClassification.yml
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
When cherry-picking the commit, I noticed:
\342\200\216indicated some weird invisible character!I must have done this when copy-pasting the file path from GitHub's web UI?
Rename the file to the correct name: