Per-repository account assignment is the mechanism that makes multi-account work practical in GITmaxed. Instead of a global "active account" you flip all day, each repository stores its own account binding, and every operation on that repository uses the bound identity automatically.
Where the assignment lives
Each repository record in GITmaxed stores an assigned-account field (the account's login name). The field is part of GITmaxed's local repository database — not the repository's .git directory — so cloning or sharing a repository never exports account bindings.
Setting the account manually
- Select the repository in the left sidebar.
- In the Changes sidebar header you will see the account picker (avatar and username).
- Choose the account that should act for this repository from the list of signed-in accounts.
- The choice applies immediately and permanently — the next fetch or push uses the new account with no further action.
Automatic assignment
When you first add a repository from disk, GITmaxed analyzes the folder path:
- If the path contains a folder matching a signed-in account's login, the repository is auto-assigned to that account.
- Repositories cloned through GITmaxed land in account-named folders by default, so auto-assignment works out of the box.
How the binding is used
The assigned account determines which token authenticates:
- fetch / pull / push
- clone operations started from that repository's context
- creating and viewing pull requests for that repository
- any other operation that talks to GitHub.com on the repository's behalf
If no account is assigned, GITmaxed falls back to your primary (first-added) signed-in account, and the picker shows that state clearly.
Why per-repository beats a global switcher
- Zero risk of wrong-identity pushes — the repository itself carries the identity.
- No context-switching overhead — open the repository you want; the identity follows.
- Concurrent work — pull from a work repo and a personal repo minutes apart without touching account settings.
FAQ
Does the assignment travel with the repository if I move the folder?
The binding is stored in GITmaxed's database keyed by the repository. After moving, re-add the repository from its new location — folder-based auto-assignment usually restores the binding, otherwise you re-pick once.
Can two repositories in the same folder use different accounts?
Yes — manual assignment is per repository. Folder matching only runs as a first-add suggestion.
What happens if I remove the assigned account?
The repository shows an unassigned state and falls back to the primary account until you assign another.
Can teammates see which account I use?
No — the binding is local to your machine and never changes the remote or commit metadata seen by others.
No comments:
Post a Comment