Resolve redirections

[keith]

Often when users rename there github accounts there is a linter failure when they add a new spec. It fails saying something like:

- ERROR | The source of the spec doesn't match with the recorded ones. Source: `https://github.com/supermarin/ObjectiveRecord.git`. Previous: `https://github.com/mneorr/Objective-Record.git`
Please contact the specs repo maintainers if thelibrary changed location.
-> The spec cannot be accepted.

from

It would be great if the linter could follow the redirections to see that the URL is actually the same in both cases.

[neonichu]

I think this is a good idea.

Potential risk: someone sets up a redirect to the original when pushing the new spec and changes it afterwards, so it might be wise to just to this for GitHub URLs?

[keith]

Yes. It might be a good idea to limit this to Github to Github changes since users don't have that kind of control over the redirections.

[fabiopelosin]

I think that the current implementation (with @neonichu) is good enough... Pretty soon we will be moving to Trunk and the authentication should prevent the hijacking this check is designed to prevent.