github: clone a specific branch

最新推荐文章于 2025-12-03 12:05:17 发布
原创 最新推荐文章于 2025-12-03 12:05:17 发布 · 546 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#git #github #branch #clone

本文介绍如何使用Git克隆远程仓库的指定分支到本地。通过使用`git clone -b`命令，可以轻松地将所需的分支从远程仓库拉取并设置为当前工作分支。

Git clone will behave copying remote current working branch into local.

if you want to clone a specific branch,there is another method:

git clone -b <branch> <remote_repo>

Example:

git clone -b my-branch git@github.com:user/myproject.git

Alternative (no public key setup needed):

git clone -b my-branch https://git@github.com/username/myproject.git

git从零开始（一）：github新建仓库和本地拉取提交
m0_46544495的博客
10-09 1499
新建github仓库并拉取到本地操作
Git: clone a specific branch
sbdayong的专栏
05-17 284
Git: clone a specific branch   git clone -b &lt;branch&gt; &lt;remote_repo&gt; Example: git clone -b my-branch git@github.com:user/myproject.git Alternative (no public key setup needed): ...
mac系统github如何clone到本地与上传
热门推荐
NevesZhang
03-17 1万+
一、安装Git MAC 上安装Git主要有两种方式 首先查看电脑是否安装Git，终端输入： git 安装过则会输出： usage: git [--version] [--help] [-C &lt;path&gt;] [-c name=value] [--exec-path[=&lt;path&gt;]] [--html-path] [--man-path] [--info...
git只从server上clone一个branch，而不clone整个仓库的指令
auspark的专栏
06-16 1383
git只从server上clone一个branch，而不clone整个仓库的指令： 如果不加参数--single-branch，而只用了-b参数，那还会clone整个仓库。只是会在clone后，自动的checkout为-b所指定的分支。
git clone 的--single-branch和--depth参数
glenshappy的专栏
03-04 6711
当项目过大时，git clone时会出现error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504 Gateway Time-out的问题，如下图 解决方法很简单，在git clone时加上--depth=1即可解决 depth用于指定克隆深度，为1即表示只克隆最近一次commit. 这种方法克隆的项目只包含最近的一次commit的一个分支，体积很小，即可解决文章开头提到的项目过大导致Timeou.
How to use git flow to checkout a specific feature branch from a remote repository
在路上
09-26 125
How to use git flow to checkout a specific feature branch from a remote repository
GitHub创建代码仓库、分支、pull和push
keke10的专栏
05-21 1059
我自己对这个副本进行修改，当修改完成之后，我想把我这个修改提交给项目的作者的时候，这时候，我就需要在这两个代码仓库之间，使用“Pull requests”，原作者看到“Pull requests”觉得改得还挺好，就可以把“Pull requests”合并。因为我们想要为开源项目做贡献，所以我们是贡献者，但是我们没有项目的push权限，我们想要进行更改，这时候可以创建一个“Fork”，可以获取代码仓库当前状态的一个副本，将项目移动到自己的代码仓库（我们所在的组织中），那么这个副本的应用权就是我自己了。
Git克隆分支–如何克隆特定分支
cumian9828的博客
08-20 4431
git克隆分支Unlike older centralized version control systems such as SVN and CVS, Git is distributed. Every developer has the full history and control of their code locally or remotely. They can also acces...
【Github CLI】Take GitHub to the command line
风高秋月白，雨霁晚霞红
01-20 2737
gh：Github官方命令行工具。让你拥有更快的clone、pr、issue体验。
MAC上Git安装与GitHub基本使用
点滴记忆
11-27 3567
目录 安装git 创建ssh key、配置git 提交本地项目到GitHub 一、安装Git MAC 上安装Git主要有两种方式 首先查看电脑是否安装Git，终端输入： git 安装过则会输出： WMBdeMacBook-Pro:~ WENBO$ git usage: git [--version] [--help] [-C <path>] [-c name...
git clone -b master https://ghproxy.com/https://github.com/LinuxCNC/linuxcnc.git git clone https://github.com/LinuxCNC/linuxcnc.git
07-23
我们正在处理用户的问题：“我想克隆特定分支和主仓库的意图 请问git clone specific branch and main repository” 用户想要克隆一个特定分支以及主仓库（可能是整个仓库，包括所有分支？）。注意，用户提到了...
clone https://github.com/skddyj/bemfacp -r bemfa/custom_components/bemfa /root/homeassistant/custom_components
08-26
要克隆指定 GitHub 仓库的特定分支或路径到本地目录，可以使用 `git clone` 命令结合 `--branch` 和 `--depth` 参数来实现。以下是具体步骤和命令示例： ### 克隆特定分支 如果只想克隆仓库中的特定分支，可以使用 ...
H:\>git clone -h usage: git clone [<options>] [--] <repo> [<dir>] -v, --[no-]verbose be more verbose -q, --[no-]quiet be more quiet --[no-]progress force progress reporting --[no-]reject-shallow don't clone shallow repository -n, --no-checkout don't create a checkout --checkout opposite of --no-checkout --[no-]bare create a bare repository --[no-]mirror create a mirror repository (implies --bare) -l, --[no-]local to clone from a local repository --no-hardlinks don't use local hardlinks, always copy --hardlinks opposite of --no-hardlinks -s, --[no-]shared setup as shared repository --[no-]recurse-submodules[=<pathspec>] initialize submodules in the clone --[no-]recursive[=<pathspec>] alias of --recurse-submodules -j, --[no-]jobs <n> number of submodules cloned in parallel --[no-]template <template-directory> directory from which templates will be used --[no-]reference <repo> reference repository --[no-]reference-if-able <repo> reference repository --[no-]dissociate use --reference only while cloning -o, --[no-]origin <name> use <name> instead of 'origin' to track upstream -b, --[no-]branch <branch> checkout <branch> instead of the remote's HEAD -u, --[no-]upload-pack <path> path to git-upload-pack on the remote --[no-]depth <depth> create a shallow clone of that depth --[no-]shallow-since <time> create a shallow clone since a specific time --[no-]shallow-exclude <revision> deepen history of shallow clone, excluding rev --[no-]single-branch clone only one branch, HEAD or --branch --no-tags don't clone any tags, and make later fetches not to follow them --tags opposite of --no-tags --[no-]shallow-submodules any cloned submodules will be shallow --[no-]separate-git-dir <gitdir> separate git dir from working tree --[no-]ref-format <format> specify the reference format to use -c, --[no-]config <key=value> set config inside the new repository --[no-]server-option <server-specific> option to transmit -4, --ipv4 use IPv4 addresses only -6, --ipv6 use IPv6 addresses only --[no-]filter <args> object filtering --[no-]also-filter-submodules apply partial clone filters to submodules --[no-]remote-submodules any cloned submodules will use their remote-tracking branch --[no-]sparse initialize sparse-checkout file to include only files at root --[no-]bundle-uri <uri> a URI for downloading bundles before fetching from origin remote
11-26
从你提供的 `git clone -h` 输出可以看出，这是 Git 的完整帮助信息，列出了 `git clone` 命令支持的所有选项。其中特别重要的是关于子模块（submodules）的参数说明。 我们来详细解释这些参数中与 `--recursive` ...
#!/bin/bash # # git $Id$ #:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: # Copyright (c) 2002-2025 The ROMS Group ::: # Licensed under a MIT/X style license ::: # See License_ROMS.md ::: #::::::::::::::::::::::::::::::::::::::::::::::::::::: Hernan G. Arango ::: # ::: # ROMS Compiling BASH Script ::: # ::: # Script to compile an user application where the application-specific ::: # files are kept separate from the ROMS source code. ::: # ::: # Q: How/why does this script work? ::: # ::: # A: The ROMS makefile configures user-defined options with a set of ::: # flags such as ROMS_APPLICATION. Browse the makefile to see these. ::: # If an option in the makefile uses the syntax ?= in setting the ::: # default, this means that make will check whether an environment ::: # variable by that name is set in the shell that calls make. If so ::: # the environment variable value overrides the default (and the ::: # user need not maintain separate makefiles, or frequently edit ::: # the makefile, to run separate applications). ::: # ::: # Usage: ::: # ::: # ./build_roms.sh [options] ::: # ::: # Options: ::: # ::: # -b Compile a specific ROMS GitHub branch ::: # ::: # build_roms.sh -j 10 -b feature/kernel ::: # ::: # -g Compile with debug flag (slower code) ::: # ::: # build_roms.sh -g -j 10 ::: # ::: # -j [N] Compile in parallel using N CPUs ::: # omit argument for all available CPUs ::: # ::: # -pio Compile with PIO (Parallel I/O) NetCDF library ::: # Otherwise, it used standard NetCDF library (slower) ::: # ::: # build_roms.sh -pio -j 10 ::: # ::: # -p macro Prints any Makefile macro value. For example, ::: # ::: # build_roms.sh -p FFLAGS ::: # ::: # -noclean Do not clean already compiled objects ::: # ::: # Notice that sometimes the parallel compilation fail to find MPI ::: # include file "mpif.h". ::: # ::: # The branch option -b is only possible for ROMS source code from ::: # https://github.com/myroms. Such versions are under development ::: # and targeted to advanced users, superusers, and beta testers. ::: # Regular and novice users must use the default 'develop' branch. ::: # ::: #:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: export which_MPI=openmpi # default, overwritten below g_flags=0 parallel=0 pio_lib=0 clean=1 dprint=0 branch=0 command="build_roms.sh $@" separator=`perl -e "print '<>' x 50;"` export MY_CPP_FLAGS= while [ $# -gt 0 ] do case "$1" in -g ) shift g_flags=1 ;; -pio ) shift pio_lib=1 ;; -j ) shift parallel=1 test=`echo $1 | grep '^[0-9]\+$'` if [ "$test" != "" ]; then NCPUS="-j $1" shift else NCPUS="-j" fi ;; -p ) shift clean=0 dprint=1 debug="print-$1" shift ;; -noclean ) shift clean=0 ;; -b ) shift branch=1 branch_name=`echo $1 | grep -v '^-'` if [ "$branch_name" == "" ]; then echo "Please enter a ROMS GitHub branch name." exit 1 fi shift ;; * ) echo "" echo "${separator}" echo "$0 : Unknown option [ $1 ]" echo "" echo "Available Options:" echo "" echo "-b branch_name Compile specific ROMS GitHub branch name" echo " For example: build_roms.sh -b feature/kernel" echo "" echo "-g Compile with debugging flags, slower code" echo "" echo "-j [N] Compile in parallel using N CPUs" echo " omit argument for all avaliable CPUs" echo "" echo "-pio Compile with the PIO NetCDF Library" echo "" echo "-p macro Prints any Makefile macro value" echo " For example: build_roms.sh -p FFLAGS" echo "" echo "-noclean Do not clean already compiled objects" echo "" echo "${separator}" echo "" exit 1 ;; esac done # Set the CPP option defining the particular application. This will # determine the name of the ".h" header file with the application # CPP definitions. export ROMS_APPLICATION=UPWELLING # Set a local environmental variable to define the path to the directories # where the ROMS source code is located (MY_ROOT_DIR), and this project's # configuration and files are kept (MY_PROJECT_DIR). Notice that if the # User sets the ROMS_ROOT_DIR environment variable in their computer logging # script describing the location from where the ROMS source code was cloned # or downloaded, it uses that value. if [ -n "${ROMS_ROOT_DIR:+1}" ]; then export MY_ROOT_DIR=${ROMS_ROOT_DIR} else export MY_ROOT_DIR=${HOME}/ocean/repository/git fi export MY_PROJECT_DIR=${PWD} # The path to the user's local current ROMS source code. # # If downloading ROMS locally, this would be the user's Working Copy Path. # One advantage of maintaining your source code copy is that when working # simultaneously on multiple machines (e.g., a local workstation, a local # cluster, and a remote supercomputer), you can update with the latest ROMS # release and always get an up-to-date customized source on each machine. # This script allows for differing paths to the code and inputs on other # computers. export MY_ROMS_SRC=${MY_ROOT_DIR}/roms # Set path of the directory containing makefile configuration (*.mk) files. # The user has the option to specify a customized version of these files # in a different directory than the one distributed with the source code, # ${MY_ROMS_SRC}/Compilers. If this is the case, you need to keep these # configurations files up-to-date. export COMPILERS=${MY_ROMS_SRC}/Compilers #export COMPILERS=${HOME}/Compilers/ROMS #-------------------------------------------------------------------------- # Set tunable CPP options. #-------------------------------------------------------------------------- # # Sometimes it is desirable to activate one or more CPP options to run # different variants of the same application without modifying its header # file. If this is the case, specify each options here using the -D syntax. # Notice also that you need to use shell's quoting syntax to enclose the # definition. Both single or double quotes work. For example, # #export MY_CPP_FLAGS="${MY_CPP_FLAGS} -DAVERAGES" #export MY_CPP_FLAGS="${MY_CPP_FLAGS} -DDEBUGGING" # # can be used to write time-averaged fields. Notice that you can have as # many definitions as you want by appending values. if [ $pio_lib -eq 1 ]; then export MY_CPP_FLAGS="${MY_CPP_FLAGS} -DPIO_LIB" fi #-------------------------------------------------------------------------- # Compiler options. #-------------------------------------------------------------------------- # # Other user defined environmental variables. See the ROMS makefile for # details on other options the user might want to set here. Be sure to # leave the switches meant to be off set to an empty string or commented # out. Any string value (including off) will evaluate to TRUE in # conditional if-statements. export USE_MPI=on # distributed-memory parallelism export USE_MPIF90=on # compile with mpif90 script #export which_MPI=intel # compile with mpiifort library #export which_MPI=mpich # compile with MPICH library #export which_MPI=mpich2 # compile with MPICH2 library #export which_MPI=mvapich2 # compile with MVAPICH2 library export which_MPI=openmpi # compile with OpenMPI library #export USE_OpenMP=on # shared-memory parallelism #export FORT=ifx export FORT=ifort #export FORT=gfortran #export FORT=pgi if [ $g_flags -eq 1 ]; then export USE_DEBUG=on # use Fortran debugging flags fi export USE_LARGE=on # activate 64-bit compilation #-------------------------------------------------------------------------- # Building the ROMS executable using the shared library is not recommended # because it requires keeping track of the matching libROMS.{so|dylib} # which is located in the Build_roms or Build_romsG directory and will be # lost and/or replaced with each new build. The option to build the shared # version of libROMS was introduced for use in model coupling systems. #-------------------------------------------------------------------------- #export SHARED=on # build libROMS.{so|dylib} export STATIC=on # build libROMS.a export EXEC=on # build roms{G|M|O|S} executable # ROMS I/O choices and combinations. A more complete description of the # available options can be found in the wiki (https://myroms.org/wiki/IO). # Most users will want to enable at least USE_NETCDF4 because that will # instruct the ROMS build system to use nf-config to determine the # necessary libraries and paths to link into the ROMS executable. export USE_NETCDF4=on # compile with NetCDF-4 library #export USE_PARALLEL_IO=on # Parallel I/O with NetCDF-4/HDF5 if [ $pio_lib -eq 1 ]; then export USE_PIO=on # Parallel I/O with PIO library fi # If any of the coupling component use the HDF5 Fortran API for primary # I/O, we need to compile the main driver with the HDF5 library. #export USE_HDF5=on # compile with HDF5 library #-------------------------------------------------------------------------- # If coupling Earth System Models (ESM), set the location of the ESM # component libraries and modules. #-------------------------------------------------------------------------- source ${MY_ROMS_SRC}/ESM/esm_libs.sh ${MY_ROMS_SRC}/ESM/esm_libs.sh #-------------------------------------------------------------------------- # If applicable, use my specified library paths. #-------------------------------------------------------------------------- export USE_MY_LIBS=no # use system default library paths #export USE_MY_LIBS=yes # use my customized library paths MY_PATHS=${COMPILERS}/my_build_paths.sh if [ "${USE_MY_LIBS}" == "yes" ]; then source ${MY_PATHS} ${MY_PATHS} fi #-------------------------------------------------------------------------- # The rest of this script sets the path to the users header file and # analytical source files, if any. See the templates in User/Functionals. #-------------------------------------------------------------------------- # # If applicable, use the MY_ANALYTICAL_DIR directory to place your # customized biology model header file (like fennel.h, nemuro.h, ecosim.h, # etc). export MY_HEADER_DIR=${MY_PROJECT_DIR} export MY_ANALYTICAL_DIR=${MY_PROJECT_DIR} # Put the binary to execute in the following directory. export BINDIR=${MY_PROJECT_DIR} echo "" echo "${separator}" # Stop if activating both MPI and OpenMP at the same time. if [ -n "${USE_MPI:+1}" ] && [ -n "${USE_OpenMP:+1}" ]; then echo "" echo "You cannot activate USE_MPI and USE_OpenMP at the same time!" exit 1 fi # Put the f90 files in a project specific Build directory to avoid conflict # with other projects. if [ -n "${USE_DEBUG:+1}" ]; then export BUILD_DIR=${MY_PROJECT_DIR}/Build_romsG export myBIN=${BINDIR}/romsG else if [ -n "${USE_OpenMP:+1}" ]; then export BUILD_DIR=${MY_PROJECT_DIR}/Build_romsO export myBIN=${BINDIR}/romsO elif [ -n "${USE_MPI:+1}" ]; then export BUILD_DIR=${MY_PROJECT_DIR}/Build_romsM export myBIN=${BINDIR}/romsM else export BUILD_DIR=${MY_PROJECT_DIR}/Build_roms export myBIN=${BINDIR}/romsS fi fi # For backward compatibility, set deprecated SCRATCH_DIR to compile # older released versions of ROMS. export SCRATCH_DIR=${BUILD_DIR} # If necessary, create ROMS build directory. if [ ! -d ${BUILD_DIR} ]; then echo "" echo "Creating ROMS build directory: ${BUILD_DIR}" echo "" mkdir $BUILD_DIR fi # Go to the users source directory to compile. The options set above will # pick up the application-specific code from the appropriate place. if [ $branch -eq 1 ]; then # Check out requested branch from ROMS GitHub. if [ ! -d ${MY_PROJECT_DIR}/src ]; then echo "" echo "Downloading ROMS source code from GitHub: https://github.com/myroms" echo "" git clone https://www.github.com/myroms/roms.git src fi echo "" echo "Checking out ROMS GitHub branch: $branch_name" echo "" cd src git checkout $branch_name # If we are using the COMPILERS from the ROMS source code # overide the value set above if [[ ${COMPILERS} == ${MY_ROMS_SRC}* ]]; then export COMPILERS=${MY_PROJECT_DIR}/src/Compilers fi export MY_ROMS_SRC=${MY_PROJECT_DIR}/src else echo "" echo "Using ROMS source code from: ${MY_ROMS_SRC}" echo "" cd ${MY_ROMS_SRC} fi #-------------------------------------------------------------------------- # Compile. #-------------------------------------------------------------------------- # Remove build directory. if [ $clean -eq 1 ]; then echo "" echo "Cleaning ROMS build directory: ${BUILD_DIR}" echo "" make clean fi # Compile (the binary will go to BINDIR set above). if [ $dprint -eq 1 ]; then make $debug else echo "" echo "Compiling ROMS source code:" echo "" if [ $parallel -eq 1 ]; then make $NCPUS else make fi HEADER=`echo ${ROMS_APPLICATION} | tr '[:upper:]' '[:lower:]'`.h echo "" echo "${separator}" echo "GNU Build script command: ${command}" echo "ROMS source directory: ${MY_ROMS_SRC}" echo "ROMS header file: ${MY_HEADER_DIR}/${HEADER}" echo "ROMS build directory: ${BUILD_DIR}" echo "ROMS executable: ${myBIN}" if [ $branch -eq 1 ]; then echo "ROMS downloaded from: https://github.com/myroms/roms.git" echo "ROMS compiled branch: $branch_name" fi echo "ROMS Application: ${ROMS_APPLICATION}" FFLAGS=`make print-FFLAGS | cut -d " " -f 3-` echo "Fortran compiler: ${FORT}" echo "Fortran flags: ${FFLAGS}" if [ -n "${MY_CPP_FLAGS:+1}" ]; then echo "Added CPP Options: ${MY_CPP_FLAGS}" fi echo "${separator}" echo "" fi 配置ROMS编译选项：进入roms目录，查看ROMS/External目录下的build_roms.sh脚本，根据需要修改编译选项，例如启用MPI并行计算、指定编译器等。 需要修改哪些内容呢？
07-19
### 配置 ROMS 编译选项的方法与关键点 在配置 ROMS（Regional Ocean Modeling System）的编译选项时，用户通常需要根据目标平台和需求修改编译参数，例如启用 MPI 并行计算、指定编译器类型、设置 NetCDF 路径等。...
JShielder
最新发布
weixin_42113341的博客
12-03 66
安装步骤。
Day4 AtomGit口袋工具开发1.0
Rene_ZHK的博客
12-02 728
Day4 AtomGit口袋工具开发1.0
flutter环境配置中遇到的问题
2501_93573368的博客
11-30 1542
本文详细介绍了Flutter环境配置中的环境变量设置问题。首先解释了系统变量和用户变量的区别：系统变量全局生效需管理员权限，用户变量仅对当前用户有效。重点说明了Path变量的核心作用，即让系统能够找到并运行程序。然后具体演示了配置鸿蒙SDK环境变量的步骤，包括在Path中添加DevEco Studio相关路径、新建DEVECO_SDK_HOME变量等操作。最后指导了如何下载适配鸿蒙的Flutter SDK，并完成相应的环境变量配置。文章通过清晰的步骤说明和配图，帮助初学者理解环境变量的概念并顺利完成配置。
【Git】Git的配置与使用（非常详细）
2302_79323248的博客
12-01 986
本文详细介绍了Git版本控制工具的核心概念、工作流程及常用操作。主要内容包括：Git的基本概念（仓库、工作目录、暂存区等）；Git的安装与环境配置步骤；常用命令如初始化仓库、添加文件、提交修改、查看日志等；vi编辑器的基本使用方法；以及Git工作区与暂存区的状态转换机制。文章通过图文结合的方式，帮助读者快速掌握Git的基础操作，适合Git初学者学习参考。
webRTC IPC客户端UniApp版编程指南
metaRTC的博客
12-03 286
yangipcclient新增uni-app版本sdk和demo，可同时适配移动端android/ios，为提升rtc性能，视图采用最底层的Surface/UIView，所有视图渲染和rtc处理都在C++/Object C里封装。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值