Retiring upstream repo
I started my most recent project in one repository, but then I changed the name of the project and started a new repository. In order to get things up-to-date quickly, I forked the first repo, then marked it as read-only.
https://github.com/0rora/0rora is the official repo, and has been forked from the read-only https://github.com/luxe-app/luxe. I control both repos.
Now, when I try to create a pull request on the new repo, github will redirect to the original repo and attempt to create a pull request there.
How should I properly retire the original repo? Will things go bad if I simply delete it?
github
asked Feb 11 at 5:39
SynessoSynesso
3011212
add a comment |
I started my most recent project in one repository, but then I changed the name of the project and started a new repository. In order to get things up-to-date quickly, I forked the first repo, then marked it as read-only.
https://github.com/0rora/0rora is the official repo, and has been forked from the read-only https://github.com/luxe-app/luxe. I control both repos.
Now, when I try to create a pull request on the new repo, github will redirect to the original repo and attempt to create a pull request there.
How should I properly retire the original repo? Will things go bad if I simply delete it?
github
asked Feb 11 at 5:39
SynessoSynesso
3011212
add a comment |
I started my most recent project in one repository, but then I changed the name of the project and started a new repository. In order to get things up-to-date quickly, I forked the first repo, then marked it as read-only.
https://github.com/0rora/0rora is the official repo, and has been forked from the read-only https://github.com/luxe-app/luxe. I control both repos.
Now, when I try to create a pull request on the new repo, github will redirect to the original repo and attempt to create a pull request there.
How should I properly retire the original repo? Will things go bad if I simply delete it?
github
asked Feb 11 at 5:39
SynessoSynesso
3011212
I started my most recent project in one repository, but then I changed the name of the project and started a new repository. In order to get things up-to-date quickly, I forked the first repo, then marked it as read-only.
https://github.com/0rora/0rora is the official repo, and has been forked from the read-only https://github.com/luxe-app/luxe. I control both repos.
Now, when I try to create a pull request on the new repo, github will redirect to the original repo and attempt to create a pull request there.
How should I properly retire the original repo? Will things go bad if I simply delete it?
github
github
asked Feb 11 at 5:39
SynessoSynesso
3011212
asked Feb 11 at 5:39
SynessoSynesso
3011212
asked Feb 11 at 5:39
SynessoSynesso
3011212
asked Feb 11 at 5:39
SynessoSynesso
3011212
asked Feb 11 at 5:39
SynessoSynesso
3011212
3011212
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1404318%2fretiring-upstream-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 Super User!
- 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%2fsuperuser.com%2fquestions%2f1404318%2fretiring-upstream-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
