shahar1 opened a new pull request, #74116: URL: https://github.com/apache/airflow/pull/74116
closes: #74114 The current `breeze workflow-run sync-staging-to-main` is quite brittle, as someone might accidentally remove docs artifacts from other releases. This PR adds a print of commits that don't exist on `main` as part of the confirmation. <details><summary>AI Summary</summary>`breeze workflow-run sync-staging-to-main` force-resets `staging` to `main` in apache/airflow-site and apache/airflow-site-archive, dropping everything only on `staging`. Until now the confirmation was a generic warning, so a release manager could not see whether `staging` held docs prepared for another release. Before the prompt, the command now compares `staging` to `main` in each repo with `gh api repos/<repo>/compare/main...staging` (no clone). If `staging` has commits that are not on `main`, it lists them per repo (short SHA and subject) and the prompt states how many commits will be dropped. The default answer stays NO and `--answer yes` works as before. If `staging` is equal to or behind `main`, nothing changes. If the comparison fails (network, missing branch), it prints a warning and falls back to the previous prompt. </details> --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Sonnet 5.5, orchestrated by Fable 5.1) Generated-by: Claude Code (Sonnet 5.5, orchestrated by Fable 5.1) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
