Problem Description
When GITmaxed Desktop is opened, the application always selects the default GitHub account, regardless of which repository was last used or which account is associated with that repository.
This creates a risk of accidentally pushing commits using the wrong account.
Current Behavior
- GITmaxed Desktop already has repository-to-account recognition functionality.
- When a repository is selected manually, the application correctly identifies and switches to the associated GitHub account.
- However, this recognition does not happen automatically when the application starts.
Example Scenario
- Account A is set as the default account.
- Repository /demo-repo belongs to Account B.
- You work on Repository /demo-repo and close GITmaxed Desktop.
- Later, you reopen GITmaxed Desktop.
- The application automatically selects Account A instead of Account B.
- If you quickly push changes without checking the selected account:
- The commit/push may be performed using Account A.
- Account A can accidentally appear as a contributor to Repository X.
Expected Behavior
GITmaxed Desktop should automatically detect the repository currently opened on startup and select the correct associated GitHub account.
The account selection logic should work the same way during startup as it already works when manually selecting a repository.
Suggested Fix
On application launch:
- Detect the currently loaded repository.
- Check the repository's associated GitHub account.
- Automatically switch to that account.
- Only use the default account when no repository-specific account is detected.
Why This Matters
Multi-account users can accidentally contribute with the wrong identity because the application opens with the default account instead of the repository owner account.
This creates:
- Incorrect contributor attribution.
- Confusing GitHub activity history.
- Possible accidental pushes from the wrong account.
Additional Notes
Currently, the workaround is:
- Manually select the correct GitHub account after opening the app, or
- Switch to another repository and return, which triggers account recognition.
After this manual action, GITmaxed Desktop works correctly.
The issue is only with automatic account recognition during application startup.
⚠️ Warning: If the account is not checked on the first app opening, this version may accidentally expose your private GitHub account in the contributor list of another account's repository.
Problem Description
When GITmaxed Desktop is opened, the application always selects the default GitHub account, regardless of which repository was last used or which account is associated with that repository.
This creates a risk of accidentally pushing commits using the wrong account.
Current Behavior
Example Scenario
Expected Behavior
GITmaxed Desktop should automatically detect the repository currently opened on startup and select the correct associated GitHub account.
The account selection logic should work the same way during startup as it already works when manually selecting a repository.
Suggested Fix
On application launch:
Why This Matters
Multi-account users can accidentally contribute with the wrong identity because the application opens with the default account instead of the repository owner account.
This creates:
Additional Notes
Currently, the workaround is:
After this manual action, GITmaxed Desktop works correctly.
The issue is only with automatic account recognition during application startup.