Can you change a GIT upstream to preserve commit history for a repo?
A colleague was asking if there was a way to fork a repo in Gitlab, but i was thinking that if in the CLI, he clones a repo and changes the upstream, he could essentially push a local repo and its commit history to a new repo located in our git server.
Am I right or is there something else I should do?
Right now we have a repo he can only access and a new repo created by him.
Ideally, i was thinking to preserve commit history, instead of just copying files over. I was thinking just changing the upstream, and pushing would do just that.
git gitlab
asked Nov 12 '18 at 18:19
Fallenreaper
3,93583380
add a comment |
A colleague was asking if there was a way to fork a repo in Gitlab, but i was thinking that if in the CLI, he clones a repo and changes the upstream, he could essentially push a local repo and its commit history to a new repo located in our git server.
Am I right or is there something else I should do?
Right now we have a repo he can only access and a new repo created by him.
Ideally, i was thinking to preserve commit history, instead of just copying files over. I was thinking just changing the upstream, and pushing would do just that.
git gitlab
asked Nov 12 '18 at 18:19
Fallenreaper
3,93583380
1
That'll do it.
– jthill
Nov 12 '18 at 19:35
add a comment |
A colleague was asking if there was a way to fork a repo in Gitlab, but i was thinking that if in the CLI, he clones a repo and changes the upstream, he could essentially push a local repo and its commit history to a new repo located in our git server.
Am I right or is there something else I should do?
Right now we have a repo he can only access and a new repo created by him.
Ideally, i was thinking to preserve commit history, instead of just copying files over. I was thinking just changing the upstream, and pushing would do just that.
git gitlab
asked Nov 12 '18 at 18:19
Fallenreaper
3,93583380
A colleague was asking if there was a way to fork a repo in Gitlab, but i was thinking that if in the CLI, he clones a repo and changes the upstream, he could essentially push a local repo and its commit history to a new repo located in our git server.
Am I right or is there something else I should do?
Right now we have a repo he can only access and a new repo created by him.
Ideally, i was thinking to preserve commit history, instead of just copying files over. I was thinking just changing the upstream, and pushing would do just that.
git gitlab
git gitlab
asked Nov 12 '18 at 18:19
Fallenreaper
3,93583380
asked Nov 12 '18 at 18:19
Fallenreaper
3,93583380
asked Nov 12 '18 at 18:19
Fallenreaper
3,93583380
asked Nov 12 '18 at 18:19
Fallenreaper
3,93583380
asked Nov 12 '18 at 18:19
Fallenreaper
3,93583380
3,93583380
1
That'll do it.
– jthill
Nov 12 '18 at 19:35
add a comment |
1
That'll do it.
– jthill
Nov 12 '18 at 19:35
1
1
That'll do it.
– jthill
Nov 12 '18 at 19:35
That'll do it.
– jthill
Nov 12 '18 at 19:35
add a comment |
0
active
oldest
votes
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%2f53267936%2fcan-you-change-a-git-upstream-to-preserve-commit-history-for-a-repo%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53267936%2fcan-you-change-a-git-upstream-to-preserve-commit-history-for-a-repo%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
1
That'll do it.
– jthill
Nov 12 '18 at 19:35