Disruption with creation of fine grained personal access tokens
This summary is created by Generative AI and may differ from the actual content.
Overview
On August 10, 2026, between 17:16 and 18:21 UTC, users were unable to create new fine-grained personal access tokens (FG PAT) through the GitHub website. When users submitted the FG PAT creation form, they were returned to the FG PAT list without an error message and no token was created. Creating classic personal access tokens and editing or deleting existing FG PATs were not affected. The incident was caused by a change to how the website loads certain front-end JavaScript that was enabled at 17:15 UTC, which interacted with an issue in the token creation form's confirmation step, preventing it from running and causing the final submission to never complete. GitHub mitigated the incident by disabling the change at 18:21 UTC, after which token creation recovered immediately.
Impact
Users were unable to create new fine-grained personal access tokens for approximately 65 minutes. Classic personal access token creation and management of existing tokens were not affected.
Trigger
A change to how the website loads certain front-end JavaScript was enabled for all users at 17:15 UTC.
Detection
Users reported being unable to create fine-grained personal access tokens. When attempting to create a new token, users were redirected back to the token overview page without an error message, but the token was not created.
Resolution
GitHub disabled the JavaScript loading change at 18:21 UTC, which immediately restored token creation functionality. Long-term resolutions include adding monitoring and alerting for anomalies in FG PAT creation success rate and removing the issue in the token creation form's confirmation step.
Root Cause
The change to how the website loads certain front-end JavaScript interacted with a pre-existing issue in the token creation form's confirmation step that prevented it from running, causing the final submission that creates the token to never complete. Because the page still loaded and the server returned a normal response, the failure produced no error message.