►
From YouTube: GitLab Virtual Meetup - Introducción a Git y GitLab
Description
Link a la Presentación y al paso a paso del ejercicio Práctico.
https://docs.google.com/presentation/d/1dxC9Xy1kB2DDiAKuvfIlyW62ba5MGGpA1Clh45gG-GE/edit?usp=sharing
This is a recording of the GitLab Virtual meetup from 2020/06/10 featuring Ricardo Amarilla.
We would love for you to contribute to our virtual meetups.
You can find upcoming virtual meetups and resources to plan your own here: https://about.gitlab.com/community/virtual-meetups/
We want to hear your ideas for topics. Remote? Security? Contributing to OS? Email suggestions to evangelists@gitlab.com.
We also love when community members present at GitLab meetups. Send an email to evangelists@gitlab.com if you’re interested in being the featured speaker at a future remote meetup.
A
My
name
is
part
of
the
team
and
an
important
point
during
this
session
that
we
will
be
doing
today,,
which
is
our
virtual
sight
in
Spanish,.
I,
want
to
share
with
you
our
code
of
conduct,,
which
I
am
sharing
with
you.
Sharing
through
the
facebook
chat,
so
that
you
can
review
it.
We
also
welcome
this
virtual
look
initiative,
and
the
idea
of
this
look
is
to
give
you
a
little
introduction
to
what
gets
and
hitler
has
been,
and
it
just
seems
like
what
we
are
going
to
be
seeing
with
riccardo
is
just
like
git.
A
To
start,
we
will
have
a
session
with
ricard.
At
the
end,
we
will
divide
ourselves
into
several
groups
to
continue
the
session
of
the
viewpoint
so,
like
you,
He
introduced
Ricardo,
Amarilla,
manager
for
Latin
America
and
who
will
be
joining
us
today,,
giving
precisely
this
introduction
to
git
and
Ricardo's
kit.
B
Good
afternoon,
Romer,,
thanks
for
the
introduction.
Welcome
to
everyone.,
Good
afternoon,,
Latin
America.
The
idea,
is
to
make
a
short
introduction.
of
what
is
going
to
be
and
what
is
on
the
agenda
is
going
to
be.
This
I
am
going
to
go
through
very
quickly.
Today's
objective
is
to
do
the
practical
exercise
that
will
have
the
step
by
step
in
this
layout.
B
God
is
Ricardo
Amarilla
office
in
Asunción,
Paraguay
I
am
technical
account
manager
for
Latin
America,
since
January
of
this
year
very
happy
to
be
in
the
plan
and
very
happy
to
be
here
with
you
today.
In
the
slide,
you
will
find
the
links
so
that
you
can
contact
me
if
you
wish,
quickly
seeing
an
introduction
to
what
it
is
and
there
I
would
like
to
have
a
little
feedback
from
you
through
the
chat
in
who
knows
git,,
who
does
not
know
a
gif
with
a
1.
B
A
B
That
it
works
for
everyone,
even
if
It's,
that
they
don't
know,
thank
God.
They
are
responding,
well,,
it's
going
well.
It's
a
tool
that
helps
us
to
control.
The
versions
of
changes
to
the
files
in
kit.
It
doesn't
require
a
continuous
connection
to
a
version
control
system.
That's,
why
we
say
it's
a
distributed
system
so
that
we
can
work
with
the
project
in
each
developer
to
be
able
to
work
in
a
local
copy
of
the
repository
and
then
push
the
changes
to
this
remote
repository.
We
will
also
explain
how
to
do
it
later
now.
B
That
is
why
We
said
it's
responsive
and
being
fast
and
reliable,
takes
away
the
lesson
of
modern
teams,
in
that
it
allows
us
to
keep
track
of
each
and
every
change
made
to
repositories
in
our
project
files
and
makes
it
easy
to
audit
correcting
them
or
simply
reverting
those
changes
and,
as
the
main
point
of
all
in
the
collaboration
is
what
makes
it
so
that
it
is
chosen.
That
is
very
important.
The
collaboration
that
is
achieved
with
guild-
and
it
is
also
very
reliable
because
it
protects
the
integrity
of
the
files.
B
It
makes
tracking
and
uses
cryptographic.
Algorithms,
such
as
one
that
protects
the
source
code
from
these
changes
and
provides
full
tracking
now.
So
we
can
know
who,
how,
when
and
why
these
changes
were
made
very
easily.
And
finally,
we
say
that
it
is
flexible,
allows
each
developer,
use
tools,
for
example,
command
line
a
cl
and
to
interact
with
the
repository
like.
It
is
also
possible
to
use
other
graphical
tools
on
top
of
git
to
use
its
power.
B
B
Line
of
code
development,
right,-
and
we
tell
the
committee
the
committing
a
code
change
was
then
new
with
bits
commits
on
code.
Changes
are
put
into
the
history
and
it
takes
into
account
the
change
history
and
that
change
history.
Does
it
for
each
branch.
So
when
we
commit
a
change
to
the
repository,
what
we
are
doing
is
putting
a
point
in
the
history
of
that
current
branch.
B
So
when
ap
We
apply
our
own
changes,,
what
we
do
is
modify
the
history,,
not
only
the
files,,
but
also
the
history
of
the
files,
and
I
want
to
be
very
clear
about
that,
because
what
we
have
in
the
beige
guide
data
is
the
history
of
changes
in
a
physical
main
branch
of
a
project
is
usually
a
special
branch
that
we
call
master.
This
branch
can
be
protected
against
changes
that
anyone
can
make
then
only
authorized.
B
People
will
be
able
to
make
changes
directly
to
that
branch,
and
we
will
talk
later
about
the
flow
to
make
these
changes.
So
when
we
talk
about
labels
or
tags,
allow
us
to
name
not
the
files
but
specific
points
in
time
of
a
branch
including
the
lover,
for
example,
version
1.
We
will
no
longer
have
to
make
a
change
in
a
file
copy
and
paste
the
file
in
another
directory
and
change
the
name
of
the
bq
file.
No,
no.
B
This
is
not
how
it
works,
and
what
we
do
is
mark
that
record
in
time,
with
a
specific
touch
can
be
version
1.0
and
2.0
3.0
and
after
subsequent
changes,
it
is
possible
to
revert
easily.
If
there
is
a
need,
then
that
is
how
a
tag
works,
a
tag
we
are
marking
not
the
file,
but
the
point
in
time
in
which
we
saw
how
to
check
out
the
concept
of
cecco,.
There
are
git
and
it
refers
to
obtaining
the
local
copies
of
a
repote
repository
in
which
we
want
to
provide
changes.
B
The
repository
can
be
hosted
on
a
remote
server.
We
will
talk
about
after
that
too,
and
we
can
create
a
new
branch
or
just
move
to
a
branch
in
the
repository
in
which
we
want
to
make
the
changes
in
each
branch.
As
we
said
in
a
separate
line
of
code
development
that
allows
us
to
make
changes
to
the
code
in
a
way
and
without
worrying
that
it
can
affect
a
branch
that
might
be
in.
B
Production
as
we
make
changes
to
this
branch
and
confirm
them
by
a
committee,
we
can
take
push
the
changes
in
the
repository
and
create
a
new
record
of
the
time
of
these
changes
and
to
send
these
changes
to
the
source
repository
from
which
we
first
got
it.
We
use
what
we
call
push
there.
We
send
the
records
of
the
changes
of
the
repository,
also
to
move
it
better
then,
but
that
is
very
important
and
the
work
test.
B
Some
other
terminology,
when
we
talk,
for
example,
about
files
in
suits
or
what
are
untracked
means
that
any
new
files
on
the
word
page
place
on
your
computer's
wordpress
that
you
are
adding
to
the
repository
in
have
not
yet
been
added
here
for
tracking.
Sometimes
there
are
files
that
are
intentionally
left
untracked
for
having
information
such
as
passwords
or
some
other
information
that
we
do
not
need
to
track
through
from
git,
in
that
it
can
also
be
done
in
a
configurable
way.
B
A
B
B
B
Here
I
have
the
project
that
we
have
developed,
so
we
can
do
the
exercise
step
by
step.
Don't
worry,
n,
or
do
you
have
to
do
anything
yet
now,
but
I
would
like
to
show
you
how
it
works.
Is
the
concept
of
the
working
directories,
the
stage
areas
inti
local
repository
here
I
have
an
open
terminal
that
is
open
in
a
folder
on
my
local
computer,
which
is
the
virtual
mental.
What
if
I'm
done
all
the
files
in
this
folder
is
empty
here
we
can
also
see
for
those
who
know
the
visual
studio.
B
How
can
they
determine
that?
There
is
no
file
in
this
folder
and
what
I
am
going
to
do
now?
A
clone
I
am
going
to
do
the
first.
The
first
step
I,
have
my
a
I,
have
my
project
in
a
remote
repository
and
I'm,
going
to
bring
it
to
my
computer
that
we
do
through
a
clone
that
we
can
use
ssh
or
acer
htc
in
this
case,
I'm
going
to
do
it
by
ss
h
back
here,
so
that
this
works
on
your
computers.
B
B
The
repository
yes
I
am
authenticated
here,
com
and
authentication
token,
and
with
the
ssh
security
certificates
so
for
sale.
I
can
download
these
files
on
my
local
file
machine
before
I
was
not
there.
So
where
are
we
in
the
process?
Today?
We
are
here:
I
made
the
clone
in
the
first
step
and
I
have
the
files
to
modify
them
in
my
work
environment.
On
my
current
machine,.
It
can
also
be
done,.
You
can
create
an
empty
project
in
git
lab,,
have
a
project
on
your
computer
and
push
it
in
this
case.
B
from
your
work
to
here.
With
this
case,
we
follow
the
first
flow
now
I
want
to
make
some
changes
in
a
file.
A
basic
change.
I
can
first
use,
for
example,
a
seven
status
command
and
I
can,
but
first
I
must
access
the
hello
latam
folder
that
is
listed
inside
this
repository
now,
something
that
was
not
there
before.
B
Tells
me
that
I
am
in
the
master
branch
in
the
master
branch
and
that
in
my
branch
it
is
in
c
Concordance
with
the
remote
branch,
that
is,
there
is
no
change
introduced,.
There
is
no
difference
between
the
remote
repository
and
remains
and
thorium,
the
local
thing
that
happens
when
I
edit
one
of
these
files,
for
example,.
The
raid,
here
is
an
explanation
of
what
this
project
is.
I
am
going
to
put
the
date.
B
Yes,
yes,
I
save
the
file
with
command
and
something
back
to
a
status.
I
am
always
working
on
the
master
branch.
I
can
tell
and
I
have
the
indication
that
the
changes
are
not
in
the
stage
environment
to
eat
and
they
are
in
red.
What
do
you
want
say
this
that
we
are
here?
We
add
changes
to
the
files,
but
we
have
not
yet
added
these
changes
to
the
staying
area.
What
we
are.
B
B
B
B
B
Great
now,
I'll
go
quickly
to
an
introduction
to
hitler
s
not
yet
in
the
practical
exercise,
and
hitler
is
a
complete
boxing
platform
in
a
single
application.
We
cover,
and
it
is
stage
of
the
software
development
cycle,
from
planning
to
monitoring
the
applications
and
their
environments
for
more
details
of
each
of
each
stage.
You
can
follow
the
link.
B
In
the
simplest
form
and
drag
flow
consists
of
a
master
branch
where
all
the
code
that
will
be
deployed
to
production
resides
from
here,
each
developer
can
create
a
feature.
Branch
or
different
lines
of
development
lines
is
basically
a
copy
of
the
master
branch.
At
that
point
in
time
where
we
began
to
carry
out
the
work
a
month
ago,
integrate
these
changes
to
master
and
deploy
in
a
way
continuous
to
do
is
the
most
automatic
way
possible
that
these
changes
quickly
reach
production
oceans.
B
B
Also,
this
radio
speed
and
speed
in
taking
changes
to
master
avoids
us
conflicts
in
the
months
after
when
different
teams
or
developers
make
changes
at
the
same
time
in
the
same
files,
then,
the
idea
is
to
create
parallel
branches
from
the
master,
to
the
master,
make
changes
very
quickly
and
integrate
as
quickly
as
possible.
Kong
production
and
We
make
this
integration
possible
by
allowing
you
to
collaborate
with
keys
for
planning,
including
the
planning
teams,
through
the
months
after
for
code
changes,
including
developers,
and
also
with.
B
Continuous
deployment
and
continuous
integration
ssd
tools
on
continuous
delivery
in
for
different
environments,
production,
we
pre-
production
or
whatever
you
want
to
call
it,,
which
also
makes
it
possible
for
us
to
integrate
operations
teams,
for
example,
and
those
are
the
advantages
of
automating,
a
pipeline,,
accelerating
delivery
and
reducing
and
reducing
the
times
in
which
a
change
is
adopted
in
the
production
environments
within
guitar
flow
elmer
was
something
very
important
where
all
the
collaboration
and
code
changes
happen
on
the
floors
from
the
planning.
What
we
can
say
is
that
we
set
the
scope
of
the
changes.
B
What
is
the
scope?
What
we
want
to
give
to
these
changes
and
within
that
site?
What
we
are
going
to
do
in
the
practical
exercise
is
to
create
a
mercedes
well
to
make
the
changes
in
the
code
and
collaborate
with
the
team
in
those
fields.
At
once
that
we
are
satisfied
with
the
changes
that
we
want
to
introduce
in
the
local
repository
we
can
share
with
the
team
and
ask
for
suggestions
for
improvement.
While
this
happens,
we
can
add
an
an
indication
that
the
work
is
in
progress
that
world
process
in
English.
B
While
this
indicator
is
displayed,
it
is
not
possible
to
integrate
the
main
branch
code,
because
the
changes
in
your
peers
are
not
yet
ready.
Your
colleagues
can
comment
in
the
months
after
in
a
general
way
here
in
the
comments
below
or
directly
in
the
lines
of
code,
so
that
they
can
quickly
identify
what
it
refers
to
and
be
able
to
evaluate.
If
those
changes
will
improve
the
code
or
not.
It
is
also
possible
to
start
discussions
where
suggestions
are
made
where
they
are
made
by
For
example,.
B
They
want
comments
on
the
code
and
as
long
as
these
discussions
are
not
resolved,,
it
is
not
possible
to
integrate
the
code
either,,
so
this
allows
them
to
collaborate
very
quickly.
Among
the
entire
team.,
It
is
also
possible
to
see
the
changes
introduced
by
each
committee
here
on
a
single
screen,
the
red
line.
We
can
see
a
field,
a
line
that
has
been
removed
from
this
file
or
and
in
the
green
line.
We
can
see
a
line
that
has
been
added.
B
This
is
the
flow
that
we
are
going
to
see
in
the
practical
exercise,
the
practical
exercise
in
which
now
my
colleagues
are
going
to
share
both
the
slide
where
it
is
the
step
by
step,
as
the
project
on
which
we
are
going
to
base
ourselves
simply
consists
of
a
page
hosted
in
guild,
a
dot
com.
The
page
hosted
in
git
the
dotcom.
B
B
B
B
We
are
going
to
go
to
this
project
the
project
that
I
prepared
in
isla
dotcom
in
my
other
account,
and
we
are
going
to
fork
a
force
that
is
a
copy
because
it
is
a
copy
of
the
entire
local
repository
and
I
am
going
to
take
it
to
my
workspace.
As
you
can
see
here,
the
workspace
is
in
ricardo
amarilla
in
bar
hello,
the
cam
and
I
am
going
to
take
it
to
my
workspace
in
this
user.
B
And
having
this
result,
the
project
is
done
forums
satisfactorily
once
I
have
this
message.
What
I
am
going
to
do
is
I
am
going
to
remove
the
relationship
here
we
can
see
that
there
is
a
relationship
between
the
source
project
and
the
project.
Currently,
I
am
going
to
remove
this
relationship
to
avoid
sending
changes
to
the
source
project
by
mistake..
To
do
it,
I
go
to
this
symbol
of
advanced
general
tools,.
B
B
B
B
Piece
of
information
to
add
in
a
piece
of
information
in
which
it
makes
me
a
deployment
on
the
page
very
similar
to
the
one
we
saw
before,
but
let's
say
in
a
different
environment
once
this
work
is
finished,
I
will
be
able
to
access
the
page.
Here
we
see
that
it
is
running
on
a
kit.
The
peruvian
is
an
executor
in
different
from
the
instance.
D
in
this
case
is
a
remote
and
we
are
preparing
the
environment
to
be
able
to
deploy.
B
B
We
saw
that
it
has
already
been
successfully
completed.
We
will
go
back
to
seventh
here
in
the
pages
tool,
and
here
we
can
see
where
our
project
that
we
have
made
social
po
has
been
deployed.
Let's
follow
this
page
and
the
same
page
has
been
displayed,.
They
will
be
able
to
do
the
same
thing
by
following
this
crossbowman
of
the
project
that
we
are
going
to
do
now.
We
are
going
to
go
back
to
the
project
and
we
are
going
to
create
an
issue.
B
Purple
background:
let's
assign
it
to
myself
how
to
put
a
deadline
by
which
we
want
to
complete
the
work
we
could
assign
some
labels
in
this
case,
I
don't
have
any,
but
everything
that
refers
to
the
issues
is
for
the
project
management
of
our
team,.
So
what
we
are
going
to
do
here
is
collaborate
with
our
teams,,
whether
it
is
product
or
planning,
to
see
what
effort
we
are
going
to
put
into
these
changes
and
what
is
the
scope
of
these
changes,?
B
B
We
have
a
follow-up
of
these
tasks
that
we
need
to
do.
In
this
case,
the
scope
has
been
defined.
We
have
already
done
all
the
task.
It
is
clear
what
we
have
to
do.
What
is
the
next
step
is
where
we
are
going
to
create
a
month,
then
from
the
is
with
the
creation
of
the
verger.
Well,
it
is.
We
are
ready
to
make
the
code
changes.
The
changes
we
have
to
make
are
clear
and
we
are
going
to
apply
them
in
this
case
we
create
a
mercedez,
well,
the
verger.
B
B
Together,
if
that
is
forex,
for
example,
this
is
where
we
can
start
in
the
collaboration.
I
have
also
created
a
new
branch
different
from
the
master
that
will
be
integrated
into
the
changes
with
a
verse
in
then,
and
there
would
be
from
this
point.
I
have
two
options
to
make
the
changes
in
a
similar
way
in
my
local
environment,
such
as
using
the
webs
hitler
ite.
B
In
this
case
for
simplicity
and
because
I
don't
know,
if
everyone
has
the
bike
installed
on
their
computers,
as
well
as
a
text
editor
in
an
editor,
so
we
are
going
to
do
it
through
the
web.
We
are
going
to
open
the
web,
haiti
and
it
goes.
We
are
going
to
enter
In
an
environment
very
similar
to
the
one
that
I
had
shown
you
locally,,
but
we
have
all
the
files,.
They
were
all
the
files
in
the
repository.
In
this
case,.
B
B
We
have
a
tab
for
editing
where
I
was
before.
I
have
a
tab
to
review
the
changes
in
red.
What
has
been
changed
and
in
green
as
it
is
currently,
it
seems
perfectly
correct
to
me
what
I
am
doing
so
I
am
going
to
give
it
food
back.
I
have
a
view
to
be
able
to
do
a
last
revision
of
the
changes.
I
say
change
the
color
to
purple,
and
here
I
am
going
to
integrate
these
changes.
B
B
Here
it
joins
the
market,
the
game
the
change
I
have
made
and
I
can
request
an
approval.
As
we
see
here
is
the
market
in
progress.
There
were
converts
of
this
if,
in
this
case,
no
approval
is
required
in
case
it
is
required.
I
can
assign
a
tester
in
I,
am
going
to
assign
this
case
to
myself
and
I
am
going
to
have
it
displayed
here
that
I
have
a
month
later
pending
review
of
me
in
this
case,
ok
Ricardo.
It
seems
good
to
me.
B
We
can
collaborate
with
different
teams.
We
can
ask
for
opinions
once
it
is
ready.
The
work
is
perfect.
We
are
satisfied.
I
can
solve
what
the
working
process
status
is.
That
is
the
first
step.
I
am
not
going
to
resolve
when
resolving
in
this
case.
I
can
do
the
month,
because
I
have
permissions
for
this
for
this
repository,
but
not
everyone
can
generally
do
the
month.
So
that's
where
we
can
assign
the
person
in
charge
of
doing
the
month
and
tell
him
ok
the
changes
we
have
made.
We
think
they
are
correct.
B
Please
make
a
month
to
the
main
branch
and
well
and
we
can
directly
make
a
hit
here.
We
also
have
a
history
of
all
the
comics.
In
this
case
it
says
only
one
change,
but
I
can
make
many
more
changes
in
not
only
one
type
file
also
review
the
changes
that
I
have
made
before
approving,
as
already
speaking
as
an
on
approve,
but
as
an
executor
for
easily
reviewing
the
changes
in
an
interface.
B
Ok
as
a
tester
I
say
that
everything
is
good
and
I
give
it
a
merckx,
and
this
is
where
it
starts,
and
this
is
where
an
automatic
deployment
in
the
pipeline
starts
again.
With
this
merge
to
master.
If
we
Let's
go
to
66,,
it
says
from
the
country,,
we
can
tell
you
that
automatically,
without
manual
intervention,,
a
new
pipeline,
has
been
created
that
what
it
will
do
is
take
the
changes
to
the
production
page
directly
without
manual
intervention,.
B
B
B
B
B
A
Perfect
Ricardo.
Thank
you
very
much
for
the
explanation
and
this
introduction
to
vietnam,
as
well
as
walking
us
during
this
exercise
and
seeing
and
visualizing
just
how
We
can
do
it
with
figures,.
Equally
for
everyone.
I
am
posting
the
link
for
the
slide
again
in
the
chat,
so
you
can
see
not
only
the
content
that
Ricardo
has
shared
with
us,,
but
also
go
through
the
step
by
step
of
each
of
the
stages
with
which
Ricardo
did.
The
exercise
is
good
to
continue,.
B
A
You
will
zoom
in
on
a
small
screen
saying
that
we
are
going
to
start
this
section
of
the
group
so
that
If
you
can
enter,.
You
have
to
click
on
that
button
and
later,
when
we
are
finishing
the
group
section,
we
will
see
a
clock
that
will
count
down
and
until
the
end
this
time
we
will
return
it
again
to
this
main
session.
So
with
that
we
can
give.