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
Currently, if the internal branch has a commit that is not available in the public GitHub repository, the mirror pipeline does not sync the repository. The mirror pipeline should be updated to trigger a sync when force pushing from the public GitHub repository for release/* branches only.
The text was updated successfully, but these errors were encountered:
@Francisco-Gamino I need some clarification on your issue. Are you saying we have made a commit to Azure Devops release/* branch and you want that change to flow back into GitHub?
Or are you saying we have made a force-push to GitHub release/* branch, and that new commit is not being mirrored to Azure Devops?
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.
If you are not the original author (Francisco-Gamino) and believe this issue is not stale, please comment with /bot not-stale and I will not close it.
Currently, if the internal branch has a commit that is not available in the public GitHub repository, the mirror pipeline does not sync the repository. The mirror pipeline should be updated to trigger a sync when force pushing from the public GitHub repository for
release/*
branches only.The text was updated successfully, but these errors were encountered: