Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
G
git-jso
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
DOSCH Philippe
git-jso
Commits
9c299e91
Commit
9c299e91
authored
3 years ago
by
Philippe Dosch
Browse files
Options
Downloads
Patches
Plain Diff
Récupération branche distante
parent
5017d4e9
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
advancedgit.tex
+17
-0
17 additions, 0 deletions
advancedgit.tex
with
17 additions
and
0 deletions
advancedgit.tex
+
17
−
0
View file @
9c299e91
...
...
@@ -335,6 +335,23 @@
%======================================================================
\frame
{
\frametitle
{
Récupérer une nouvelle branche distante
}
\begin{itemize}
\item
Particulièrement intéressant dans le cadre de pull/merge request
\item
Scénario : un contributeur a créé une nouvelle branche, qu'on
souhaite récupérer en local
\item
La syntaxe générale est (pour harmoniser les noms locaux/distants)
\\
\ex
{
git checkout -b nouvbranche origin/nouvbranche
}
ou
\ex
{
git switch -C nouvbranche origin/nouvbranche
}
?
\end{itemize}
}
%======================================================================
\frame
{
\frametitle
{
Pousser une branche vers une autre
}
\begin{itemize}
\item
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment