Ctrl + P> Type "History" > Enter the file path.
If you wanna "merge" (rebase style)
branch_2, just drag and drop
branch_1and choose the option "Rebase branch_2 onto branch_1". It will merge commits from
branch_2step by step and put the "new" commit on
branch_2onto the top of merged commits from
1branch_1: A -- B -- C -- D -- E 2branch_2: A -- F -- G -- H 3 4# After rebasing (branch_2 onto branch_1) 5branch_1: unchanges 6branch_2: A -- B -- C -- D -- E -- F -- G -- H
- Sign in with any account in GK.
- Add new profile (with private acc)
- Click on Integrations → Connect to private account & Generate a new SSH token.
- Refresh things to see the changes.
Best practice: Create and sign in with a Gitkraken account. Don't worry if you have use the option "sign in with Google", you can create with that email too. After sign in via email (not via google), you can create and connect different profiles with different github accounts.
Suppose that we work with
[email protected](personal) and
[email protected](working). There are personal repos and working repos.
- Sign in to GK with ~
any profile (suppose personal)~ Gitkraken account.
- Make 2 different profiles (one for personal, one for working).
- Connect to Github account in each profile (need to approve + generate a new SSH key for each). In case it automatically opens the same browser (with the same github account) for 2 different profiles, you can copy the URL and paste to another browser with a different github account.
- Each profile will have a separated workspace.
- Everytime choosing a profile, a new workspace with its repos will be loaded.
If problems? In case you cannot integrate automatically to different Github accounts in the same session of Gitkraken.
- Keep integrate auto for 1 account.
- Create a seprate SSH keys.
- In the Integrations tab, link to the files created in previous step.
- Clone projects by ssh url instead.
✳️ thi-ideta wants to push to dinhanhthi on some repo, besides add thi-ideta's public key to the SSH, dinhanhthi must add thi-ideta to the "Collaborators" of that repo!