-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move this repo to the LSE-Methodology organization #2
Comments
From @amatsuo on September 20, 2017 13:26 Isn't it just doing this? https://help.github.com/articles/transferring-a-repository-owned-by-your-personal-account/ |
Normally yes but for this transfer there are also yaml config files and possibly some hard coded URL references. Plus there is the move from gh-pages part. |
From @amatsuo on September 21, 2017 10:46 The website is up with old contents. I also updated the travis settings on several .yml files. This would already work once a travis hook is set up. Could you make Travis watch the repo "LSE-Methodology/MY451"? |
I can provide permissions for you to set this up - what do you need? |
From @amatsuo on September 21, 2017 11:21 I need your travis login, if you don't mind. |
@amatsuo moved it and it appeared to be ok. Note that no local processing is required - it should work by simply pushing a markdown file and the CI will build the website. |
From @chmue on September 26, 2017 18:12 Ok, great! Are there any plans to incorporate the changes from the fork here, then delete the fork and transfer this to LSE-Methodology? The reason I'm asking is that this is still the main repo and the one at the LSE-Methodology is just a fork. That means you cannot do certain things on the new (forked) repo such as reporting issues and text search of the content. |
Yes that’s entirely the idea, to get it out of my user account and move it entirely to the LSE-Methodology organization. If it’s working in LSE-Methodology, we can just delete it from my account. (I assume this will not kill the “downstream” fork, if that even makes sense in git-speak.) |
From @chmue on September 26, 2017 18:17 Hm, I'm actually not sure off the top of my head if there are any issues with just deleting upstream. The Git history itself should be safe in the fork but I'm not sure if GH does some special things to upstream/fork that would break. |
Sounds like we should make it public first. I’ll do that now. |
From @chmue on September 26, 2017 18:27 Maybe it's easier to just merge the changes in the fork and then transfer ownership? Edit: Ah no, sorry! I should have read until the very end of the page. You want to make the repo public and then delete it right after that such that the private fork gets its own history tree. |
From @chmue on September 26, 2017 18:40 I think it worked! The other repo is not a fork anymore. The issues seem to be missing but I am not sure if you have to add an issue tracker separately. We might need to copy over the issues from here by hand. I'm happy to look into this if you give me full access to the other repo. |
Done. |
From @chmue on September 27, 2017 13:1 Ok. I do have the right access for |
See Slack on the brexit team |
The move should be complete now. I was only able to copy over the open issues so we lose the closed ones but I think that should be ok. If that is ok, you should be able to delete the old |
From @kbenoit on September 20, 2017 13:15
@amatsuo could you move this to the LSE-Methodology organization? This will involve some YAML changes and maybe a few other configuration changes.
Since we started this, it's become possible to publish from a designated sub directory, making the use of the
gh-pages
branch unnecessary. Might be worth using that structure.Thanks!
Copied from original issue: kbenoit/coursepack-bookdown#21
The text was updated successfully, but these errors were encountered: