Skip to content

Create forks for upstream contributions (knit) - #264

Open
marc-merino wants to merge 2 commits into
mainfrom
knit/create-forks-for-upstream-contributions
Open

marc-merino wants to merge 2 commits into
mainfrom
knit/create-forks-for-upstream-contributions

Conversation

@marc-merino

@marc-merino marc-merino commented Oct 15, 2026 •

Copy link
Copy Markdown
Collaborator

Knit Bundle

View bundle

This PR is part of Knit bundle create-forks-for-upstream-contributions.

See the other review objects in this bundle:

Bundle id: create-forks-for-upstream-contributions
Bundle title: Create forks for upstream contributions

knit fork creates or reuses your fork of each project repository and points
origin's push URL at it; fetches stay on upstream. knit init, project add,
clone, sync pull --repos, pull, bundle pull and handoff in fork a GitHub
repository only when you cannot push to it, so a contributor's project can be
handed to the upstream organization unchanged. --fork, --no-fork and --owner
override the choice. When Knit can't tell, the checkout still succeeds and
names `knit fork <id>`. knit project add accepts a clone URL.

sv project visibility <project> [public|private] shows and changes a
project's visibility.
A bundle pushed from a fork checkout leaves the fork in the Knit project's
repository list under the member's id. Clone, pull and handoff now skip any
listed repository whose id belongs to a member but whose address does not,
so people who clone a handed-over project get the upstream repositories.

Knit-Group: kg_20261015_4559e3
Knit-Bundle: create-forks-for-upstream-contributions

This branch has not been deployed

No deployments
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