[BUG] Cancel button unresponsive when adding Git account — username/email dialog cannot be dismissed

[syntaxerron]

Description

When adding a new account via Fork > Preferences > Accounts > Add Account > Git, a dialog appears prompting for a username and email address. During this state, the Cancel button is non-interactive and cannot be clicked. Pressing ⌘Q also has no effect — the app does not quit or dismiss the dialog.

After waiting for an indeterminate amount of time, the Cancel button eventually becomes clickable.

Steps to Reproduce

1. Open Fork
2. Go to Preferences > Accounts
3. Click Add Account and select Git
4. Observe the username/email dialog that appears
5. Immediately attempt to click Cancel or press ⌘Q

Expected Behavior

The Cancel button should be immediately interactive, allowing the user to dismiss the dialog at any time. Pressing ⌘Q should also quit the app or at minimum dismiss the dialog.

Actual Behavior

• Cancel button is unresponsive immediately after the dialog opens
• ⌘Q has no effect
• After waiting some time (duration unclear), the Cancel button becomes clickable

Environment

• App: Fork
• OS: macOS Tahoe 26.4.1
• Fork version: 2.66.5

Additional Notes

This feels like the dialog may be performing a background operation (e.g. network call or credential check) on the main thread, blocking UI interaction until it completes.

[DanPristupov]

Click Add Account and select Git

There is no Git option there.

During this state, the Cancel button is non-interactive and cannot be clicked.

I just checked, Cancel button works in every dialog there.

Pressing ⌘Q also has no effect — the app does not quit or dismiss the dialog.

This is correct. ⌘Q is not handled when a dialog window is open.

[twomedia]

@DanPristupov I can also replicate this issue, and I think I know the cause. I think by "Git" he means "GitHub". For me, the cancel button is clickable, but only in the region highlighted in this screenshot:

After further testing, this issue only seems to happen for the "GitHub" option only, and only if the "Authentication Type" is set to "Log in on GitHub.com (OAuth)". If it's set to "Personal Access Token" the cancel button works fine. I suspect the extra "Manage Personal Access Tokens" UI is partially blocking the Cancel button when it's hidden.