-
Notifications
You must be signed in to change notification settings - Fork 302
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
properly transfer ar_track_alvar #124
Comments
IMO transferring the ownership isn't a requirement when the repository location is changed. Meanwhile I'm curious what made you think this repo is the main repo for ar_track_alvar. There's now a notice at the top page, links from wiki page are updated. If there are still info not updated we need to fix that, so please let us know. Thanks. |
Yes I saw the notices, however there is still an actual problem my suggestion would fix. Please look at the top of ros_perception/ar_track_alvar page. There is a message there:
Every single fork points to your repository, that's slightly inconvenient but there is a second problem. Next, click this to search "tag" in
As you can see, it is impossible to search in the other repository, because github thinks this is the main repository. Either transferring (the correct solution) or deleting and reuploading without a fork (which will still have the problem in all other forks) is the only way github will correctly reflect your decision to make https://github.com/ros-perception/ar_track_alvar/ the main repository, and this is the reasons I advise the transfer. It would be extremely helpful if you could take the steps in my first link to fix those problems! :-) |
I thought this was the main repo, could you transfer it so the main repo is the one others are forked from?
https://help.github.com/articles/transferring-a-repository-owned-by-your-personal-account/
The text was updated successfully, but these errors were encountered: