Previous behavior was to always require username and branch would be assumed to be default if not specified.
New behavior allows user to type emu fork switch -b cool_branch_name. The username is assumed to the current fork the user has switched to last. If the user wants to switch to another fork and branch, then the only difference is they have to type emu fork switch another_fork_user -b another_branch (add -b in front of branch).
The new print to let the user know what's happening when only branch is specified:
root@localhost:/data/$ emu fork switch -b stock_additions-075
No username specified, using current fork: shanesmiskol
Fetching shanesmiskol's latest changes...
Successfully checked out shanesmiskol/stock_additions-075 as shanesmiskol_stock_additions-075
I need to test what happens right after the user sets up fork management, so don't merge yet. I'll also bump the version and update the changelog soon.
Edit:
[x] bumped version and updated docs and changelog.
[x] just need to test what happens right after setting up fork management
Previous behavior was to always require username and branch would be assumed to be default if not specified.
New behavior allows user to type
emu fork switch -b cool_branch_name
. The username is assumed to the current fork the user has switched to last. If the user wants to switch to another fork and branch, then the only difference is they have to typeemu fork switch another_fork_user -b another_branch
(add-b
in front of branch).The new print to let the user know what's happening when only branch is specified:
I need to test what happens right after the user sets up fork management, so don't merge yet. I'll also bump the version and update the changelog soon.
Edit: