During the investigation of #99 I found out that github doesn't redirect after a project is renamed. For example, Nagasaki45/saffran-stimuli was recently renamed to Nagasaki45/saffran-replication, but going to the old link still works and returned the new page without redirecting. It means that the Krihelinator can't rely on redirects for determining the name of the repo.
From now on, updating repo names will be the task of the scraper. This will be implemented as part of #99.
This ticket is for removing the redirection handling all together, it should be safe. In the worst case, the pipeline will crash on any redirect, but that's OK :-).
This is a mistake. There are still redirects when a project is migrated to another user / organization. Revert the commit but change the code not to update the name during the process.
During the investigation of #99 I found out that github doesn't redirect after a project is renamed. For example, Nagasaki45/saffran-stimuli was recently renamed to Nagasaki45/saffran-replication, but going to the old link still works and returned the new page without redirecting. It means that the Krihelinator can't rely on redirects for determining the name of the repo.
From now on, updating repo names will be the task of the scraper. This will be implemented as part of #99. This ticket is for removing the redirection handling all together, it should be safe. In the worst case, the pipeline will crash on any redirect, but that's OK :-).