Skip to content

ci: use orphan commits for deploy branches to reduce clone size#1603

Draft
badrishc wants to merge 1 commit intomainfrom
fix/ci-reduce-clone-size
Draft

ci: use orphan commits for deploy branches to reduce clone size#1603
badrishc wants to merge 1 commit intomainfrom
fix/ci-reduce-clone-size

Conversation

@badrishc
Copy link
Collaborator

@badrishc badrishc commented Mar 4, 2026

The gh-pages, allure_data_history, continuousbenchmark, and continuousbenchmark_net80 branches accumulate large generated files (charts data.js ~37 MiB, allure history.json ~100 MiB) across hundreds of commits. This bloats the pack file to 1.3 GiB and makes git clone extremely slow during 'receiving objects'.

Changes:

  • deploy-website.yml: add force_orphan: true to peaceiris/actions-gh-pages so gh-pages always has a single commit (was 278 commits / 15 GiB blobs)
  • nightly.yml: rewrite allure_data_history push to use an orphan commit instead of appending to history (was 987 commits / 2.15 GiB blobs)
  • New squash-benchmark-branches.yml: monthly scheduled workflow to squash continuousbenchmark and continuousbenchmark_net80 to single commits (were 114-115 commits / 7 GiB blobs combined)

The gh-pages, allure_data_history, continuousbenchmark, and
continuousbenchmark_net80 branches accumulate large generated files
(charts data.js ~37 MiB, allure history.json ~100 MiB) across hundreds
of commits. This bloats the pack file to 1.3 GiB and makes git clone
extremely slow during 'receiving objects'.

Changes:
- deploy-website.yml: add force_orphan: true to peaceiris/actions-gh-pages
  so gh-pages always has a single commit (was 278 commits / 15 GiB blobs)
- nightly.yml: rewrite allure_data_history push to use an orphan commit
  instead of appending to history (was 987 commits / 2.15 GiB blobs)
- New squash-benchmark-branches.yml: monthly scheduled workflow to squash
  continuousbenchmark and continuousbenchmark_net80 to single commits
  (were 114-115 commits / 7 GiB blobs combined)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant