Forking public Git repositories to internal Git host, and how to track upstream
I'm currently working with Puppet modules, and I'm "forking" them from their public repos to an internal Git server. Currently, my workflow is:
- Clone the public repo to my workstation
- Run
git remote rename origin upstream
- Create a new repository in the internal Git server's web UI
- Run
git remote add origin ssh://server.name/repo/path.git
- Finally, push my local clone to the internal server:
git push -u origin master
Is this the appropriate way to re-host a public repo on an internal server?
Additionally, is there anyway to share the configuration for the upstream repo automatically with anyone who clones the internal repo? Or does each user need to manually run git remote add upstream <server>?
git git-remote git-fork upstream-branch
asked Nov 14 '18 at 14:32
zymhanzymhan
10727
add a comment |
I'm currently working with Puppet modules, and I'm "forking" them from their public repos to an internal Git server. Currently, my workflow is:
- Clone the public repo to my workstation
- Run
git remote rename origin upstream
- Create a new repository in the internal Git server's web UI
- Run
git remote add origin ssh://server.name/repo/path.git
- Finally, push my local clone to the internal server:
git push -u origin master
Is this the appropriate way to re-host a public repo on an internal server?
Additionally, is there anyway to share the configuration for the upstream repo automatically with anyone who clones the internal repo? Or does each user need to manually run git remote add upstream <server>?
git git-remote git-fork upstream-branch
asked Nov 14 '18 at 14:32
zymhanzymhan
10727
add a comment |
I'm currently working with Puppet modules, and I'm "forking" them from their public repos to an internal Git server. Currently, my workflow is:
- Clone the public repo to my workstation
- Run
git remote rename origin upstream
- Create a new repository in the internal Git server's web UI
- Run
git remote add origin ssh://server.name/repo/path.git
- Finally, push my local clone to the internal server:
git push -u origin master
Is this the appropriate way to re-host a public repo on an internal server?
Additionally, is there anyway to share the configuration for the upstream repo automatically with anyone who clones the internal repo? Or does each user need to manually run git remote add upstream <server>?
git git-remote git-fork upstream-branch
asked Nov 14 '18 at 14:32
zymhanzymhan
10727
I'm currently working with Puppet modules, and I'm "forking" them from their public repos to an internal Git server. Currently, my workflow is:
- Clone the public repo to my workstation
- Run
git remote rename origin upstream
- Create a new repository in the internal Git server's web UI
- Run
git remote add origin ssh://server.name/repo/path.git
- Finally, push my local clone to the internal server:
git push -u origin master
Is this the appropriate way to re-host a public repo on an internal server?
Additionally, is there anyway to share the configuration for the upstream repo automatically with anyone who clones the internal repo? Or does each user need to manually run git remote add upstream <server>?
git git-remote git-fork upstream-branch
git git-remote git-fork upstream-branch
asked Nov 14 '18 at 14:32
zymhanzymhan
10727
asked Nov 14 '18 at 14:32
zymhanzymhan
10727
asked Nov 14 '18 at 14:32
zymhanzymhan
10727
asked Nov 14 '18 at 14:32
zymhanzymhan
10727
asked Nov 14 '18 at 14:32
zymhanzymhan
10727
10727
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Is this the appropriate way to re-host a public repo on an internal server?
Yes. The --origin option to git clone will let you remove step 2 from your workflow.
Additionally, is there anyway to share the configuration for the upstream repo automatically with anyone who clones the internal repo?
There is not. You could put together a script that would implement your desired configuration and share that with developers who will be working on the project with you.
answered Nov 14 '18 at 15:29
larskslarsks
117k19195204
Ah that's unfortunate. Thanks for the tip on cloning though! That certainly simplifies it.
– zymhan
Nov 14 '18 at 20:42
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53302610%2fforking-public-git-repositories-to-internal-git-host-and-how-to-track-upstream%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Is this the appropriate way to re-host a public repo on an internal server?
Yes. The --origin option to git clone will let you remove step 2 from your workflow.
Additionally, is there anyway to share the configuration for the upstream repo automatically with anyone who clones the internal repo?
There is not. You could put together a script that would implement your desired configuration and share that with developers who will be working on the project with you.
answered Nov 14 '18 at 15:29
larskslarsks
117k19195204
Ah that's unfortunate. Thanks for the tip on cloning though! That certainly simplifies it.
– zymhan
Nov 14 '18 at 20:42
add a comment |
Is this the appropriate way to re-host a public repo on an internal server?
Yes. The --origin option to git clone will let you remove step 2 from your workflow.
Additionally, is there anyway to share the configuration for the upstream repo automatically with anyone who clones the internal repo?
There is not. You could put together a script that would implement your desired configuration and share that with developers who will be working on the project with you.
answered Nov 14 '18 at 15:29
larskslarsks
117k19195204
Ah that's unfortunate. Thanks for the tip on cloning though! That certainly simplifies it.
– zymhan
Nov 14 '18 at 20:42
add a comment |
Is this the appropriate way to re-host a public repo on an internal server?
Yes. The --origin option to git clone will let you remove step 2 from your workflow.
Additionally, is there anyway to share the configuration for the upstream repo automatically with anyone who clones the internal repo?
There is not. You could put together a script that would implement your desired configuration and share that with developers who will be working on the project with you.
answered Nov 14 '18 at 15:29
larskslarsks
117k19195204
Is this the appropriate way to re-host a public repo on an internal server?
Yes. The --origin option to git clone will let you remove step 2 from your workflow.
Additionally, is there anyway to share the configuration for the upstream repo automatically with anyone who clones the internal repo?
There is not. You could put together a script that would implement your desired configuration and share that with developers who will be working on the project with you.
answered Nov 14 '18 at 15:29
larskslarsks
117k19195204
answered Nov 14 '18 at 15:29
larskslarsks
117k19195204
answered Nov 14 '18 at 15:29
larskslarsks
117k19195204
answered Nov 14 '18 at 15:29
larskslarsks
117k19195204
117k19195204
Ah that's unfortunate. Thanks for the tip on cloning though! That certainly simplifies it.
– zymhan
Nov 14 '18 at 20:42
add a comment |
Ah that's unfortunate. Thanks for the tip on cloning though! That certainly simplifies it.
– zymhan
Nov 14 '18 at 20:42
Ah that's unfortunate. Thanks for the tip on cloning though! That certainly simplifies it.
– zymhan
Nov 14 '18 at 20:42
Ah that's unfortunate. Thanks for the tip on cloning though! That certainly simplifies it.
– zymhan
Nov 14 '18 at 20:42
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53302610%2fforking-public-git-repositories-to-internal-git-host-and-how-to-track-upstream%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
