# Add a new worktreegit worktree add ../new-dir existing-branch# Remove a worktreegit worktree remove ../new-di
Show Changes Not Yet Staged
If you face a situation where you need to share some changes in the code base that you have made with your co-worker but you cannot yet push your changes to the remote repository, you can use the patch command of git. Here is how it works:After you have made all the changes you can run the following command:git diff > filename.patchgit diff > filename.patch will create a file that will contain all uncommitted the changes you have made so far in the code base. Then you can simple share this file with your coworker via slack,email,USB etc .You coworker will simply download you patch file and run the following command:git apply filename.patchThis would apply all the code changes you have made in the code base on your coworker’s copy of the code.
git diff featureXYZ_branch mastergit diff remotes/origin/featureXYZ_branch remotes/origin/master
Q :How will you find a list of files that has been modified in a particular commit?A : The command to get a list of files that has been changed in a particular commit is:git diff-tree –r {commit hash}• -r flag allows the command to list individual files• commit hash lists all the files that were changed or added in the commit.
git revert <commit>
Creates a new commit to revert the specified commit
Creates a new commit to revert the specified commit
There are two processes through which you can revert a commit:
1. Remove or fix the bad file in a new commit and push it to the remote repository. Then commit it to the remote repository using:
git commit –m “commit message”
2. Create a new commit to undo all the changes that were made in the bad commit. Use the following command:
git revert <commit id>
a -> b -> c -> d(HEAD)Şöyle yaparız
git revert HEADa -> b-> c -> d -> e(HEAD)
git restore README.md # same as 'git checkout -- README.md' git restore --staged README.md # same as 'git reset HEAD README.md'
git switch develop
# same as 'git checkout develop'git switch -c new-branch# same as 'git checkout -b new-branch'
> git shortlog -s -n830 Ali ...506 Ayşe ...460 Hakan ...
set-url - change the address of a remote$ git remote rename <old_name> <new_name>
$ git remote set-url <name> <new_url>
git remote show origin
$ git remote -v ocolak git@github.com:orcunc/hazelcast.git (fetch) ocolak git@github.com:orcunc/hazelcast.git (push)
git reset —mixed is used to undo changes made in the working directory and staging area.
git merge —abort helps stop the merge process and return back to the state before the merging began.
It also very common to accidentally push a few changes/files that were not supposed to be committed. Let’s say you had some config files or credentials files like AWS secrets or .pem files. These should not be pushed in the repository. One thing that many people might try in order to remove the pushed .pem from the remote repo is following:Pull the latest code from the repo.Delete the .pem fileCreate another commit with the deleted .pem filePush the changes back to remote repoHowever in the above approach we haven’t completely removed the .pem from git. You see git keeps a track of all the files that you commit. So anyone can dig into the history of git commits and access the .pem file.But git allows you to actually modify history. So the solution would be to move back to your safe commit and force push.git reset HEAD~n is a command that lets you move back to your previous n commits. So git reset HEAD~2 will take you back two commits and will show you the changes of the last two commits.git reset HEAD --hard will clean all those changes. So for example lets say you have the following commitsNow let’s say you want to remove the last two commits i.e (commit ‘Add aws secrets’ and ‘Add .pem file’)First you will go back two commits by running the following command:git reset HEAD~2Now you can remove those two commits by using the following command:git reset HEAD -- hardNow for push the code to remote and your .pem files will be deleted from history as well.
$ git reset HEAD~ //Bir önceki commite gel
$ nano <file> //Dosyayı düzelt
$ git add <file> //Dosyayı tekrar ekle
$ git commit -c ORIG_HEAD //Commitle> git --versiongit version 2.33.0.windows.2
git fetch origingit stash : Değişiklikleri rafa kaldırır ve saklargit stash apply : Rafa kaldırılan değişiklikleri yeniden uygular
git clone https://github/com/somethinggit clone git@github.com:whatever .git clone git@github.com:whatever folder-nameBu yöntem "shallow clone" diye geçer. Git clone, tüm proje geçişimini indirir ve büyük bir projede bu işlem uzun sürer. Fakat depth parametresi ile sadece en güncel versionu indirerek süreci hızlandırabilirsiniz.
git clone https://github.com/user/repository --depth 1 --branch=master ~/dir-namegit clone --recursive -c core.longpaths=true -j 20 https://a.b.c .
git config --global user.name "..."
git config --global user.email "..."
git clone https://github.com/foo.gitgit clone https://github.com/foo.git
Cloning into '...'...
Username for 'https://github.com': ...
Password for 'https://...':
The `Foo' organization has enabled or enforced SAML SSO. To access
this repository, visit https://github.com/orgs/...
and try your request again.
unable to access 'https://foo.git/': The requested URL returned error: 403git config --global credential.helper store> git remote set-url origin https://github.com/hazelcast/hazelcast-cloud-postgre-sample > git push origin master
> git push origin master:main
> git push origin --delete main To https://github.com/hazelcast/hazelcast-cloud-postgre-sample ! [remote rejected] main (refusing to delete the current branch: refs/heads/main) error: failed to push some refs to 'https://github.com/hazelcast/hazelcast-cloud-postgre-sample'
> git push origin --delete main To https://github.com/hazelcast/hazelcast-cloud-postgre-sample - [deleted] main
#Feature için yeni branch yaratgit checkout -b feature/rw-2028 rw_22.1 #Değişiklikleri commitle git commit -a -m "rw-2028 : ..." #Değişiklikleri pushla git push #Development branch'e geç git checkout rw_22.1 #Feature branch'i sil git branch -D feature/RLWY-2028
git checkout 6d4b20f81f4d17bd2a93bbcbd4eab39457e600e7 Foo.java
git diff --name-only
git reset --hard
git checkout railway_22.1 # change a branch name git branch -m release/22.1.0 # delete the branch with the old name on the remote repository git push origin --delete railway_22.1 # push the branch with the correct name git push origin -u release/22.1.0
# Create new tag at local git tag release-22.0.1 ... # Delete tag git tag -d release-22.0.1
# Delete local and push git tag release-22.0.1 git push --tags
# Delete local and push
git tag -d release-22.1.0
git push --tags# delete from remote git push origin :refs/tags/release-22.1.0 # delete from local git tag -d release-22.1.0 # recreate at local git tag release-22.1.0 # push to remote git push --tags
git config --local user.name "John Doe"
git config --local user.email john@doe.comgit config --global alias.ci commit
git config --global alias.co checkout
...$ git config --global core.editor "nano -w"git config --global credential.helper "cache --timeout=3600"git config --system credential.helper
manager-coregit credential fill protocol=https host=github.com İki defa enter'a bas
protocol=https host=github.com username=... password=...
git config -l --show-origin$ git config --global -l$ git config -luser.email=new@new.com
user.name=new-f seçeneğiÖrnek
Sadece submodule ile çalışıp doğru branch'e commit etmek için şöyle yaparız.
cd /path/to/your/parent/repo
git config -f .gitmodules submodule.<path>.branch <branch>