You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When wildcard branch protections are created in ADO, they follow a pattern of branch/* and that works for all branches like branch/test, branch/test2, etc. But also for sub-folders like branch/test/test1, branch/mysubfolder/folder1 and other nested sub-folders.
When the branch protection is migrated, it comes across as branch/* but on the GitHub side, this will only apply to branch/test and not to branch/test/test1 (won't work if there are nested sub-folders)
So what worked in ADO, because of the way ADO implements branch protection pattern matching, would break in GitHub
While there is no way for GEI to know that there are sub-folders and the pattern needs to change from branch/* to branch/**/*, we could consider just changing the all the patterns of the form branch/* to branch/**/*