-
-
Notifications
You must be signed in to change notification settings - Fork 487
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
what happened the repo's url ? #655
Comments
Yes. See #651. |
ok, thanks your confirm, and i am reading #651 . |
This is exactly what redirection is for. The status code & redirect is literally a way of saying "This thing you were looking for on this URL has now moved, the canonical location is now some other place, I'm forwarding you over there." — it makes things continue to work seamlessly (not actually breaking the old URLs) while making sure as often as possible people end up on the new URLs. I don't know what else you expect to have happen. |
well, sometime unless the ori owner confirmed, otherwise user maybe concerned the redirection was a security risk fake. |
In the case of Github transferring repositories can only be initiated by repository owners. If the original owner didn't confirm the migration there wouldn't be redirects in the first place! That or the original owner's account is completely compromised, in which case you wouldn't be able to get trustworthy confirmation anyway—and the repository could be compromised in other ways without you noticing. |
i see, but redirection did not always mean repo owner 's password had been hacked, but just the url .. |
btw: you are doing a great job - i am a little worry some classic wonderful vim plugin lost update too :) |
The @vim-scripts org was just scraping plugin sources from other sites (notably vim.org), there was no effort at maintaining them there. Everything in there should be considered a fork (or ignored). Note that this effort is not pulling everything under one account. This is an organization namespace and has multiple people listed an owners and many more members with permissions on the projects they contribute to. Every one of the projects here has multiple admins and contributors. The idea is to diversify and spread out the responsibility, not to put it under one person. I'd be happy to talk to other great classic plugins that are struggling but there are some qualifications. I'm not interested in loading up on a bunch of plugins that nobody is interested in maintaining, only in freeing up projects that are no longer primarily maintained by their original authors. There needs to be at least one active maintainer who is also willing to work with other collaborators, and the plugin has to be reasonable successful (say 1k stars or something). There are undoubtedly some other good ones out there that have lots of open PRs from active users, the original author is not actively working on, and somebody would be interested maintaining that we could consider—but this is a limited subset of all the classic plugins that have fallen by the wayside. |
um.. looks like a biz mode - a some kind foundation. |
maybe silly, but want to confirm tagbar 's repo had been transfer-ed or mirror-ed
from :
remote.origin.url=https://github.com/majutsushi/tagbar.git
to here ?though the url still under 'majutsushi' at my local, (so need confirm if needed to update) but redirect to here automaticly now ..
the ori owner transfer-ed the repo ?
The text was updated successfully, but these errors were encountered: