-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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 AR.js repositories to a github organisation #253
Comments
i never transfered the ownership of a repo... is there a risk ? i dont wanna break AR.js repo :) here is the doc from github https://help.github.com/articles/about-repository-transfers/
|
Hi,
I don't know to be honest, we should definitely investigate it!
…On Mon, Nov 20, 2017 at 3:18 PM, Jerome Etienne ***@***.***> wrote:
i never transfered the ownership of a repo... is there a risk ? i dont
wanna break AR.js repo :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#253 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AANEe03Qe5_Bjm05_OFn0MFc1JBYAVjIks5s4XwOgaJpZM4QkPsL>
.
|
We should make a list of what GH pages are in the repository and move them
to the right place first (ex. to AR-docs, or somewhere else).
Ideally i would prefer to not have GH pages in AR.js repository, only html
pages for testing purposes (for now)
And all pages/demos should be moved to AR-docs, pointing to a domain.
If this is done, then we can migrate the repos, and providing a new url to
the examples and external links.
On Mon, Nov 20, 2017 at 3:24 PM, Zoli Veres <[email protected]>
wrote:
… Hi,
I don't know to be honest, we should definitely investigate it!
On Mon, Nov 20, 2017 at 3:18 PM, Jerome Etienne ***@***.***>
wrote:
> i never transfered the ownership of a repo... is there a risk ? i dont
> wanna break AR.js repo :)
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/jeromeetienne/AR.js/issues/
253#issuecomment-345692737>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AANEe03Qe5_Bjm05_
OFn0MFc1JBYAVjIks5s4XwOgaJpZM4QkPsL>
> .
>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#253 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AANEe5GFuIxIKN0mMl98ZBPj2mx4K679ks5s4X2pgaJpZM4QkPsL>
.
|
I have done so before. TL;DR:
This redirection will persist automatically howsoever times you change the repo name / org name. Happy renaming. But that said your will have to consider the links that are hard-linked in your documentations, those are the only things that will break. That said how about a more catchy name like getarjs for the org? I have the ownership to this. I can transfer to you should you want it? Also consider dropping the |
Also, if you are moving stuff you should do so as early stage as possible. The breaks that will happen is the anybody doing a local clone of the your repo directly will have to update their remotes I guess. Forks will be fine though. |
For GitHub Pages you will have not much choice with the standard Check out https://github.com/js-org/dns.js.org and get a subdomain that suites you. A CNAME file in the Now coming back to current links like |
And I did some quick searches that confirmed my doubts. The only hack right now seems to be this workaround https://gist.github.com/domenic/1f286d415559b56d725bee51a62c24a7 |
@jeromeetienne @ZoltanVeres Hi again. Any chance that you guys are still interested in the @getarjs handle for the org name? I can hand it off to you if you are still interested. Cheers |
@raisedadead I don't think so. @jeromeetienne bought a domain for AR.js and we already created the GH organisation https://github.com/orgs/ARjs-org. We are in the process of moving stuff there. |
As I created #469, I also restarted an investigation on how to move the repo to the org. The Github Pages problem seems to still exist: I tweeted at Github support to ask, if there is newer information on this: With some additional work, and some disadvantages in another area, one could work around it. From the support response at isaacs/github#492:
So after transferring, one could create (Of course fully depends on the original repo owner's cooperation and help) But if "keep the old URLs working" is a hard requirement, and as those are linked in lots of blog posts and other places I think it should be, this would be one option. I'd be happy to put in the work here. Some context: (Let's hope GitHub support has another, simpler one.) |
closed, see related PRs. |
The text was updated successfully, but these errors were encountered: