Push from shallow clone to GitHub #145588
Replies: 1 comment
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
General
Body
Is it possible to configure a repository in GitHub to accept pushes from shallow repositories? I’ve managed to do this with bare repositories on servers that I have access to by setting the git config option receive.shallowUpdate to true. However, I haven’t been able to find anything in the settings for my GitHub repositories that exposes this option.
Ideally, I would like to push from a shallow repository to an existing GitHub repository. But if there’s a procedure that would let me use a local shallow clone and then add it as a new GitHub repository, that would work as well.
For additional context, I would like to use git bundles to transfer commits from an internal/private repository to a public GitHub repository, but I don’t want the entire history of the private repository to be public. Currently, I either rebase or apply the recent commits from the private repo onto a branch that is pushed to the public one. But it would be nice to establish consistent commit ids (without disrupting references to the current public repository).
Beta Was this translation helpful? Give feedback.
All reactions