Renaming a repository referenced in _extends breaks authorization

[andreineculau]

Problem Description

What is actually happening

Given a settings.yml file with

_extends: owner/repo:path/to/another/settings.yml

will break Probot settings when repo gets renamed to newrepo because the API response will reply with a Location response header, which probot will follow but without reusing the same Authorization request header.

What is the expected behavior

I expect Probot settings to handle repository renaming

Error output, if available

DEBUG (octokit): GitHub request: GET https://api.github.com/repos/owner/newrepo/contents/.github%2Fsettings.base.yml - 401
[347](https://github.com/owner/callingrepo/runs/3733222?check_suite_focus=true#step:7:348)
ERROR (HttpError): Must authenticate to access this API.

Context

Are you using the hosted instance of repository-settings/app or running your own?

Running my own.

If running your own instance, are you using it with github.com or GitHub Enterprise?

GHES

Version of repository-settings/app

2.1.0

Version of GitHub Enterprise

3.6.0