Skip to content
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

Open
kbenoit opened this issue Sep 27, 2017 · 19 comments
Open

Move this repo to the LSE-Methodology organization #2

kbenoit opened this issue Sep 27, 2017 · 19 comments
Assignees

Comments

@kbenoit
Copy link
Collaborator

kbenoit commented Sep 27, 2017

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

@kbenoit
Copy link
Collaborator Author

kbenoit commented Sep 27, 2017

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/

@kbenoit
Copy link
Collaborator Author

kbenoit commented Sep 27, 2017

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.

@kbenoit
Copy link
Collaborator Author

kbenoit commented Sep 27, 2017

From @amatsuo on September 21, 2017 10:46

The website is up with old contents.
https://lse-methodology.github.io/MY451/

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"?

@kbenoit
Copy link
Collaborator Author

kbenoit commented Sep 27, 2017

I can provide permissions for you to set this up - what do you need?

@kbenoit
Copy link
Collaborator Author

kbenoit commented Sep 27, 2017

From @amatsuo on September 21, 2017 11:21

I need your travis login, if you don't mind.

@kbenoit
Copy link
Collaborator Author

kbenoit commented Sep 27, 2017

From @chmue on September 26, 2017 16:42

What is the status of the transfer? Is it finished or are there still things to do?

I'm asking because I pointed Jon (@jacksojp) to the new repo so there are new changes in the fork.

@kbenoit
Copy link
Collaborator Author

kbenoit commented Sep 27, 2017

@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.

@kbenoit
Copy link
Collaborator Author

kbenoit commented Sep 27, 2017

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.

@kbenoit
Copy link
Collaborator Author

kbenoit commented Sep 27, 2017

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.)

@kbenoit
Copy link
Collaborator Author

kbenoit commented Sep 27, 2017

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.

@kbenoit
Copy link
Collaborator Author

kbenoit commented Sep 27, 2017

Deleting a private repository

When you delete a private repository, all of its private forks are also deleted

From https://help.github.com/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility/

Sounds like we should make it public first. I’ll do that now.

@kbenoit
Copy link
Collaborator Author

kbenoit commented Sep 27, 2017

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.

@kbenoit
Copy link
Collaborator Author

kbenoit commented Sep 27, 2017

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.

@kbenoit
Copy link
Collaborator Author

kbenoit commented Sep 27, 2017

Done.

@kbenoit
Copy link
Collaborator Author

kbenoit commented Sep 27, 2017

From @chmue on September 27, 2017 11:27

Could you also make me an owner of this repo, @kbenoit ? I am using this tool to move the issues. It tells me that I have the required access to LSE-Methodology/MY451 but not for this repo.

@kbenoit
Copy link
Collaborator Author

kbenoit commented Sep 27, 2017

You have admin rights, but LSE-Methodology is the "owner". If I transfer ownership then it moves to your account.

screenshot 2017-09-27 13 56 03

@kbenoit
Copy link
Collaborator Author

kbenoit commented Sep 27, 2017

From @chmue on September 27, 2017 13:1

Ok. I do have the right access for LSE-Methodology/MY451. But I don't have the right access to this repo kbenoit/coursepack-bookdown.

@kbenoit
Copy link
Collaborator Author

kbenoit commented Sep 27, 2017

See Slack on the brexit team

@chmue
Copy link
Member

chmue commented Sep 27, 2017

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 kbenoit/coursepack-bookdown repo now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants