@jamesmcnamara reported a number of 401s when using a PAT that had access to the repositories affected by a Batch Change. I spent some hours looking into this and was amazed by what I found.

That error was happening because there was a leading whitespace in the token in 1password and apparently the github credential validator doesn't care about whitespaces however when this token is being used to push a change, it becomes a problem because the URL now looks like this:

https://%20ghp_....@github.com/sourcegraph-testing/markdowns

And that's what was calling your failing batch changes with the devx token. I'll push a fix to correct this.

Test plan

• Manual testing
• Added a credential with whitespaces and confirmed that the spaces were correctly removed.

Changelog

• Whitespaces in Batch Changes credentials are trimmed before being saved to the database, this prevents 401 errors when using the token to construct an authenticated push URL.