Skip to content

Document efficient repository cloning - #1090

Open
jamesmontemagno wants to merge 1 commit into
dotnet:mainfrom
jamesmontemagno:motz-bookish-system
Open

Document efficient repository cloning#1090
jamesmontemagno wants to merge 1 commit into
dotnet:mainfrom
jamesmontemagno:motz-bookish-system

Conversation

@jamesmontemagno

Copy link
Copy Markdown
Member

Summary

  • recommend a blobless, single-branch clone for contributors who need main history
  • document a shallow, single-branch option for CI and read-only use
  • explain the history tradeoff of the shallow option

This helps users avoid downloading disconnected generated dashboard branch history without changing repository behavior or expanding the focused Actions change in #1089.

Validation

  • npx --yes markdownlint-cli2 CONTRIBUTING.md

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot AI lite review requested due to automatic review settings August 30, 2026 19:15

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟡 Changes recommended

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review tier: Lite
Findings: 1 Low severity

New issues introduced by this change (1)
Severity Finding
Low severity CONTRIBUTING.md — This section says the clone retains the main branch history, but the command clones whatever the…
What changed in this PR

Adds contributor-facing guidance to reduce clone size/transfer by avoiding generated dashboard branch history, and clarifies the tradeoff between full-history vs shallow clones.

Changes:

  • Document a blobless, single-branch clone approach intended for contributors who need main history.
  • Document a shallow, single-branch clone option intended for CI or read-only scenarios.
  • Explain that shallow clones omit older main history.
File Description
CONTRIBUTING.md Adds a “Cloning efficiently” section describing recommended clone options and their history/size tradeoffs.
Suppressed comments (1)

CONTRIBUTING.md:27

  • This section references the latest main snapshot, but the command clones whichever branch is the repository default. Consider specifying --branch main explicitly so CI/read-only guidance stays correct if the default branch changes.
git clone --depth=1 --single-branch https://github.com/dotnet/skills.git

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread CONTRIBUTING.md
contributor clone that retains the `main` branch history, use:

```bash
git clone --filter=blob:none --single-branch https://github.com/dotnet/skills.git
@github-actions

Copy link
Copy Markdown
Contributor

👋 @jamesmontemagno — this PR has 1 unresolved review thread(s). When you're ready, please address the feedback and push an update; the triage bot will pick up the next state automatically. (Add the no-stale label to silence further pings.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

waiting-on-author PR state label

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants