GitHub recently updated it's PAT (personal access token) format which
revealed a bug where the updated PAT did not work properly because the
remote was already present and therefore adding it did not update the PAT
information. This change fixes the issue by removing the remote before
adding it.
The error was also happening silently due to old uses of > /dev/null
to avoid leaking credentials on CI. Since we now running only on
HiPerGator these have been removed to make diagnosing future git
errors easier.
henrykironde
commented
3 years ago
GitHub recently updated it's PAT (personal access token) format which revealed a bug where the updated PAT did not work properly because the remote was already present and therefore adding it did not update the PAT information. This change fixes the issue by removing the remote before adding it.
The error was also happening silently due to old uses of > /dev/null to avoid leaking credentials on CI. Since we now running only on HiPerGator these have been removed to make diagnosing future git errors easier.