How to get GIT remote branch

Get GIT remote branch

Since Git is a distributed version control system, local and remote repositories may be different. Branches are also remote, but may not be local.
Let's look at the command to import a branch of a remote repository into a local repository.

1. Remote View remote repositories

The local repository may not have all the branches of the remote. You can view the list of branches in the remote repository with the following command.
git branch -r
[root@localhost myapp]# git branch -r
  origin/dev
  origin/master
  origin/release

2. View the remote repository branch source

You don't need to have the same source locally in the remote repository branch. If you just want to see it, checkoutyou can do it temporarily with a remote branch . checkoutThe command is to switch to a different branch. If you enter the remote branch name here, you can temporarily checkout the remote branch.
git checkout [원격 브랜치 이름]
If the remote branch name is, origin/releaseyou can do the following:
[root@localhost myapp]# git checkout origin/release
Note: checking out 'origin/release'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

[root@localhost myapp]# git branch
* (detached from origin/release)
  master
After checking out, if you check with the branch command, * (detached from origin/release)you can see that it floats with. This branch will disappear when you check out another branch.
[root@localhost myapp]# git checkout master
Switched to branch 'master'
[root@localhost myapp]# git branch
* master

3. remote repository branch to the local branch checkoutto

If you want to permanently track a branch of a remote repository in a local branch, you can checkout with the following command.
git checkout -t [원격브랜치명]
If the remote branch name is, origin/releaseyou can do this:
[root@localhost myapp]# git checkout -t origin/release
Branch release set up to track remote branch release from origin.
Switched to a new branch 'release'
[root@localhost myapp]# git branch
  master
* release
When you do this, the remote branch name and the local branch name are checked out the same.
Sometimes there are multiple remote repositories, or if you overlap the local branch name that I created, you may need to rename the local branch. You can do it
with the name of the branch you want with the following command checkout:
git checkout -b [생성할 브랜치 이름] [원격 브랜치 이름]
If you want to receive a remote origin/releasebranch as a local my_releasebranch checkout:
[root@localhost myapp]# git checkout -b my_release origin/release
Branch my_release set up to track remote branch release from origin.
Switched to a new branch 'my_release'
[root@localhost myapp]# git branch
  master
* my_release

Comments

Post a Comment

Popular posts from this blog

Enabling Com Port on Hyper-V 2nd Generation VM / Windbg

Image
To test the UEFI boot environment, I created a second generation virtual machine in Hyper-V. And I had to configure the Com port to attach the kernel debugger.  However, the Com Port device was not visible in the 2nd generation Hyper-V VM.  Invisible Com port device Hyper-V 2nd generation VM must be assigned a pipe to the Com port to be visible in the device list. 1. VM termination First, shut down the VM before working. 2. Run as Powrshell administrator Detailed configuration of Hyper-V VM can be done through Powershell command.  Run Powershell with administrator privileges.  3. set-vmcomport  Run the following command to activate the com port. set -vmcomport -vmname [VM이름] -number [COM포트번호] [파이프이름] To check the COM port to which the pipe is assigned, execute the following command. get -vmcomport -vmname [VM이름] The following is an example of command execution.  https://docs.microsoft.com/en-us/powershell/module/hyper-v/set-vmcomport?view=win10-ps
Read more

DLL Injection using CreateRemoteThread in Windows 10

Image
DLL Injection using CreateRemoteThread One of the methods of DLL injection is to create a RemoteThread and load the desired DLL into the target process.  This is one of the simplest and most widely used methods.  CreateRemoteThread You can create a thread in another process using the API. CreateRemoteThread If you browse on MSDN, you'll see the following in Remarks: https://docs.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-createremotethread   CreateRemoteThread function (processthreadsapi.h)-Win32 apps Creates a thread that runs in the virtual address space of another process. docs.microsoft.com Terminal Services isolates each terminal session by design.  Therefore,  CreateRemoteThread  fails if the target process is in a different session than the calling process. In translation, Terminal Services Pros say that if the target process is running in a different session, it will fail because the session is specified and executed
Read more

Using Overlapped I / O in DeviceIoControl

Image
Using Overlapped I / O in DeviceIoControl Various methods can be used, such as  synchronizing with events and continuously receiving events through polling, to monitor the frequent events in the kernel driver one by one in user mode  . Scenario in question Imagine that you continue to receive events with relatively simple polling.  The kernel driver queues the event that occurred, and the user mode application issues the IOCTL to retrieve the contents of the queue.  In this type of logic, the user-mode application will  While execute the same loop as  DeviceIoControl and will continue to communicate with the driver by calling. while ( true ) { BOOL ret = DeviceIoControl(hDevice, IOCTL_RECV, &data, sizeof (DATA), 0 , 0 ,&dwReturn, NULL ); if (ret) { // 처리.. } } DeviceIoControl Blocking 발생 In the previously used logic,  DeviceIoControl blocking occurs  until an event occurs in the kernel driver  .  DeviceIoControl Blocking occurs in the user m
Read more