How to checkout branch of remote git, 깃 리모트 브랜치 체크아웃

To check out a branch from a remote Git repository, you can follow these steps:

1. Fetch the remote branches

First, ensure that your local repository is aware of the remote branches by using git fetch. This updates your local references to the remote branches.

git fetch origin

2. Check out the remote branch

Once the remote branches are fetched, you can check out the desired branch using git checkout -b and specifying the remote branch.

Command:

git checkout -b <local-branch-name> origin/<remote-branch-name>

Explanation:

  • <local-branch-name>: The name you want to give to your local branch.
  • origin/<remote-branch-name>: Refers to the branch on the remote called origin (which is the default name for the main remote repository) and the branch you want to check out.

Example:

If the remote branch is called feature-branch and you want to create a local branch with the same name, you would run:

git checkout -b feature-branch origin/feature-branch

3. Alternative using git switch (Modern Method)

You can also use the git switch command (introduced in Git 2.23) to achieve the same thing:

git fetch origin
git switch -c <local-branch-name> origin/<remote-branch-name>

This is equivalent to checkout but is a clearer way to switch between branches.

Summary Steps:

  1. Fetch the latest branches: git fetch origin
  2. Check out the remote branch: git checkout -b <local-branch-name> origin/<remote-branch-name>

댓글

댓글 쓰기

이 블로그의 인기 게시물

Develop a Kafka producer to send messages to a Kafka topic

Here’s a guide and code examples to develop a Kafka producer to send messages to a Kafka topic. The examples cover both plain Kafka Producer API and Spring Kafka Producer for convenience. 1. Plain Kafka Producer API Maven Dependencies Add the Kafka client dependency in your pom.xml : < dependency > < groupId > org.apache.kafka </ groupId > < artifactId > kafka-clients </ artifactId > < version > 3.6.0 </ version > <!-- Replace with your Kafka version --> </ dependency > Java Code Example This example demonstrates producing messages to a Kafka topic using the plain Kafka Producer API. import org.apache.kafka.clients.producer.KafkaProducer; import org.apache.kafka.clients.producer.ProducerRecord; import org.apache.kafka.clients.producer.RecordMetadata; import java.util.Properties; public class KafkaMessageProducer { public static void main( String [] args) { // Configure Kafka produce...
자세한 내용 보기

Parasite of korean movie

"Parasite" directed by Bong Joon-ho. It won four Academy Awards, including Best Picture, Best Director, Best Original Screenplay, and Best International Feature Film. "Parasite" is a dark comedy-thriller that explores the theme of class conflict in modern-day South Korea. The film follows the impoverished Kim family as they infiltrate the wealthy Park family's home and try to improve their own lives by exploiting the situation. But as their plan unfolds, things start to spiral out of control, leading to unexpected and shocking consequences. It's a brilliantly crafted film with outstanding performances, a captivating storyline, and thought-provoking themes. It's definitely worth watching!
자세한 내용 보기

Using the MinIO API via curl

Using the MinIO API via curl is straightforward, as MinIO is compatible with Amazon S3 API, so most commands follow a similar syntax. Here’s a guide on how to use curl with the MinIO API for some common operations like uploading, downloading, and managing objects. Prerequisites Access Key and Secret Key : Obtain your MinIO Access Key and Secret Key. MinIO Endpoint : Know your MinIO server endpoint, e.g., http://localhost:9000 . Bucket : You may need an existing bucket name, or create a new one using the commands below. Authentication Header For requests to work with MinIO, you need to include authentication in the headers. MinIO uses AWS Signature Version 4 for signing requests. Common Examples 1. List Buckets To list all buckets in your MinIO account, use: curl -X GET \ - -url "http://localhost:9000/" \ - H "Authorization: AWS <AccessKey>:<Signature>" 2. Create a Bucket To create a new bucket, use: curl -X PUT \ - -url "htt...
자세한 내용 보기

difference between truncate and truncate_preserve in hbase

In HBase, both truncate and truncate_preserve commands are used to delete all the data in a table, but they behave differently in terms of how they handle the table’s schema and regions. 1. truncate Purpose : Deletes all data and regions in a table and then recreates it with the same schema. What It Does : When you run truncate , it: Disables the table. Deletes all data and metadata (including region splits) in the table. Drops all regions and recreates the table as a single region with the original schema. Re-enables the table. Effect on Regions : After truncate , all region splits are lost, so the table will start with only one region. This is useful for development or quick data purging but is inefficient for large tables that rely on pre-split regions for load balancing. Command Syntax : truncate 'table_name' 2. truncate_preserve Purpose : Deletes all data in a table but preserves the table’s regions and schema. What It Does : When you use truncate_...
자세한 내용 보기

What are 5 creative things I could do with my kids' art, 아이와 함께하는 창의적 놀이

Absolutely, preserving your kids' art while also finding creative ways to utilize and display it can be a wonderful solution. Here are five creative ideas to consider: Art Gallery Wall: Designate a section of a wall in your home as an art gallery. Frame selected pieces of your kids' art and arrange them in an organized or eclectic manner. You can change the display periodically to showcase different artworks, creating a rotating gallery. Customized Photo Books: Compile your children's art into a digital photo book or album. Many online services allow you to create customized photo books. Arrange the artwork, add captions, and create a keepsake that you can flip through whenever you want to reminisce. Transform into Functional Items: Turn your kids' artwork into functional items such as placemats, coasters, tote bags, or even custom-made wrapping paper. There are companies that can print your children's art onto these items, making them practical and sentime...
자세한 내용 보기

To switch to a specific tag in a Git repository

To switch to a specific tag in a Git repository, you can use the git checkout or git switch command. Here's how you can do it: 1. List Available Tags First, you may want to see a list of all available tags in the repository: git tag 2. Checkout a Specific Tag Once you know the tag you want to switch to, you can use either git checkout or git switch (if you're using a newer version of Git, which recommends git switch for checking out branches). Using git checkout : git checkout <tag- name > Using git switch (recommended for newer versions of Git): git switch -- detach <tag- name > The --detach flag is necessary because tags are not branches; they are just pointers to specific commits. Using --detach makes your HEAD point to the tag without modifying any branch. 3. Verify the Checkout After switching to the tag, verify that you're on the correct commit: git status This will show the tag you're currently on (you'll see somethi...
자세한 내용 보기

Kafka consumer in a Spring Boot application using a scheduled task

Here’s how to develop a Kafka consumer in a Spring Boot application using a scheduled task for consuming messages. This approach uses @Scheduled to poll Kafka messages at fixed intervals. Step 1: Add Maven Dependencies Add the required dependencies for Spring Kafka and Scheduling in your pom.xml : < dependency > < groupId > org.springframework.kafka </ groupId > < artifactId > spring-kafka </ artifactId > </ dependency > < dependency > < groupId > org.springframework.boot </ groupId > < artifactId > spring-boot-starter </ artifactId > </ dependency > Step 2: Configure Kafka Consumer in application.yml spring: kafka: bootstrap-servers: localhost: 9092 consumer: group-id: schedule-consumer-group key-deserializer: org .apache .kafka .common .serialization .StringDeserializer value-deserializer: org .apache .kafka .common .serialization .StringDeserialize...
자세한 내용 보기

To integrate Spring Boot with your gRPC service using Gradle, Java, and Avro

To integrate Spring Boot with your gRPC service using Gradle , Java , and Avro , we’ll modify the setup to include Spring Boot dependencies. The goal is to run the gRPC service inside a Spring Boot application, making it easier to manage configurations, beans, and dependencies. Below is a complete guide to adding Spring Boot to your existing gRPC + Avro project. Updated Project Structure grpc-avro-user-service/ │ ├── src/ │ ├── main/ │ │ ├── avro/ │ │ │ └── user .avsc │ │ ├── java/ │ │ │ ├── proto/ │ │ │ │ └── UserService .proto │ │ │ └── com/example/userservice/ │ │ │ ├── UserServiceImpl .java │ │ │ ├── GrpcServerConfig .java │ │ │ └── Application .java ├── build .gradle .kts └── settings .gradle .kts Step 1: Update build.gradle.kts to Add Spring Boot Dependencies Here’s the updated build.gradle.kts to include Spring Boot along with gRPC and Avro : plugins { java id( "com.google.protob...
자세한 내용 보기

kafka polling vs listen

In Kafka, polling and listening are two different approaches to consuming messages, and they correspond to different APIs or frameworks. 1. Kafka Polling Polling refers to the use of Kafka's native poll() method in the Kafka Consumer API . It requires the consumer application to actively request messages from Kafka. Key Characteristics: Active Consumption : The application explicitly calls poll() in a loop to fetch messages. Manual Commit : Developers can choose when to commit offsets, giving fine-grained control over processing and checkpointing. Use Case : Recommended for applications where control over message consumption, offset management, or threading is critical. Example (Java): Properties props = new Properties(); props . put (ConsumerConfig.BOOTSTRAP_SERVERS_CONFIG, "localhost:9092" ); props . put (ConsumerConfig.GROUP_ID_CONFIG, "group1" ); props . put (ConsumerConfig.AUTO_OFFSET_RESET_CONFIG, "earliest" ); props . ...
자세한 내용 보기

how to delete all issues on project in sentry, 센트리 이슈 삭제하기

As of now, Sentry doesn't have a direct feature to delete all issues in bulk through the web interface. However, there are a few methods you can use to archive, resolve, or delete issues programmatically or by adjusting project settings: 1. Bulk Archive Issues from the Web Interface Though there is no mass delete option, you can bulk archive or resolve issues, which essentially hides them from active issue lists. Steps: Go to your Sentry project. In the issue list view, select the issues you want to archive or resolve. Use the "Select All" checkbox to select multiple issues. Choose "Resolve" or "Archive" from the bulk action dropdown. However, this doesn't delete the issues permanently; they will be archived or marked as resolved. 2. Adjust Retention Policy (Data Retention Settings) If you're looking to remove older issues, you can adjust the retention policy at the organization level. Sentry allows you to configure how long issue...
자세한 내용 보기