CHORE: add GitHub->ADO mirror sync pipeline

[bewithgaurav]

What

Adds the GitHub → Azure DevOps mirror sync pipeline: OneBranchPipelines/github-ado-sync.yml.

It keeps the ADO mirror (sqlclientdrivers/mssql-django) identical to GitHub, preserving full commit history (real commits, identical SHAs) via a fast-forward push — no squashed single-diff commit, and no force-push.

Design (per discussion)

• SDL-clean: the pipeline's source is the ADO mssql-django repo (checkout: self), not GitHub. It only does a plain, unauthenticated git fetch of the public GitHub repo — no GitHub service connection, no GitHub-sourced pipeline.
• History preserved: pushes GitHub main's actual commit graph (vs mssql-python's squashed replace-all).
• No hacks: zero ADO-only files, no ado-only-paths.txt. This YAML lives on GitHub and mirrors to ADO like everything else.
• No force: the ADO repo is seeded once via ADO Import repository (full history), after which every sync is a fast-forward. Needs only Build Service Contribute.
• Cadence + location match mssql-python (daily 17:00 IST, OneBranchPipelines/).

Assumes / sequencing

• Targets GitHub main — land after the dev→main default-branch switch.
• ADO side (joint step): re-import the mirror from GitHub, create the pipeline definition (source = ADO mirror), grant Build Service Contribute.

Draft until the ADO mirror is re-imported and the pipeline definition is created.

[Copilot]

⚠️ Not ready to approve

The pipeline/documentation currently hard-codes syncing GitHub dev (conflicting with the PR’s stated post-switch target of main) and uses a non-idempotent git remote add that can break on agent workspaces reused across runs.

Pull request overview

Adds an Azure DevOps (OneBranch) YAML pipeline intended to keep an ADO mirror repository in sync with the GitHub repo by fast-forwarding the mirror branch and pushing tags, while avoiding GitHub service connections.

Changes:

• Introduces OneBranchPipelines/github-ado-sync.yml defining a scheduled, ADO-sourced mirror-sync job.
• Implements a git fetch from public GitHub and a fast-forward git push back to the ADO mirror.

File summaries

File	Description
OneBranchPipelines/github-ado-sync.yml	Adds scheduled pipeline to fetch from GitHub and fast-forward push to the ADO mirror branch (plus tags).

Review details

Comments suppressed due to low confidence (2)

OneBranchPipelines/github-ado-sync.yml:12

• This file (and the script below) are written to mirror GitHub dev into ADO main, but the PR description says the pipeline should target GitHub main after the default-branch switch. Please align the branch mapping documentation here with the intended post-switch behavior so it doesn’t become stale/misleading in the mirror repo.

# Branch mapping: GitHub's default branch is `dev`; the Azure DevOps mirror's
# default/stable branch is `main` (ADO/1ES conventions -- TSA, Ownership
# Enforcer, OneBranch official builds -- expect `main`). Branch names need not
# match across the two remotes, so we sync GitHub `dev` -> ADO `main`.
#

OneBranchPipelines/github-ado-sync.yml:63

• The sync script hard-codes fetching dev and also uses git remote add github ..., which can fail on agents that reuse the workspace (remote already exists). If this pipeline is meant to run after the branch switch (GitHub main), fetch main and make the remote configuration idempotent.

    # Fetch GitHub dev's real commits + tags. Public repo -> no auth, no
    # service connection (keeps the pipeline source ADO-only for SDL).
    git remote add github https://github.com/microsoft/mssql-django.git
    git fetch --tags github dev

• Files reviewed: 1/1 changed files
• Comments generated: 1
• Review effort level: Low

Note

Your feedback helps us improve the quality of this feature.
Please use 👍 or 👎 to tell us whether this assessment is correct.