►
From YouTube: Dev Section Walkthrough - 2020-01-24
Description
Eric Brinkman provides a walkthrough of the Dev section functionality of GitLab.
A
A
Okay,
so,
as
you
can
already
see,
I'm
already
logged
in
to
get
lab
calm
and,
let's
start
by
by
making
a
group
and
a
group,
is
a
really
important
construct
inside
of
get
lab.
That
lets
you
organize
people
and
so
in
order
to
make
a
new
group
I
guess
I
have
to
click
on
your
group's
first.
Eventually,
we
should
have
a
add
group
button
here,
but
I'm
gonna
click
on
new
group
and
I'm
going
to
call
it
EB
test
group.
Two,
it
looks
like
this
will
auto-generate
my
URL
I
can
give
it
a
description.
A
Eric's
second
test
group
I'm
not
going
to
choose
a
group
avatar
and
I'm
just
going
to
go
ahead
and
make
this
public
in
typical,
get
lab
adherence
to
our
core
value
of
transparency
and
go
ahead
and
create
this
group.
So
I've
created
a
group,
a
group
as
a
collection
of
several
projects
and
subgroups
and
members
and
I'm
just
gonna
go
ahead
and
add
a
member.
A
A
Now
we
haven't
done
anything
yet
I've
just
set
up
kind
of
this
container
for
people
to
be
added,
and
so
I've
added
myself
and
Gabe
and
I
think
what
I
want
to
do
now
is
I
want
to
start
making
some
projects
and
I
can
do
that
here
in
the
group
overview
tab
by
saying
new
project
and
I
can
say
a
Eric's
web
app
and
very
similar
from
the
group
creation
screen.
The
project's
creation
screen
looks
pretty
similar
as
well.
A
Also
make
this
public
and
I
will
initialize
it
with
a
readme,
and
what
this
is
going
to
do
is
it's
going
to
make
a
new
project
in
the
EB
tester
to
group
name
space
and
you
can
see
the
URL
here.
It's
pretty
simple.
I
could
also
see
the
breadcrumbs
at
the
top
of
the
page
to
understand
where
I
am
pretty
much
at
all
times,
and
what
address
me
into
here
is
the
is
essentially
the
project
overview
page,
which
really
shows
me
a
lot
of
pertinent
details
about
the
project
and
the
repository.
A
A
There's
some
nice
little
stats
here,
number
of
commits
number
of
branches
tags
and
then
the
size
of
the
repository
and
then
also
the
branch
so
I'm
taking
a
look
at
I
can
also
add
new
files,
upload
files,
create
new
directory
and
then,
of
course,
create
new
branches
and
tags
here.
I
can
see
the
history
of
the
repository
and
then
I
can
also
go
into
our
web
IDE
straight
from
the
repository,
which
is
a
really
cool
feature,
I'll
be
walking
through
in
a
little
bit
so
right
now.
This
is
just
a
blank
project.
A
It's
not
super
useful!
So
let's
go
ahead
and
actually
make
something.
That's
a
little
bit
more
realistic
in
terms
of
an
actual
project,
so
get
lab.
Comm
I'm
gonna
go
to
my
personal
namespace,
where
I
know,
I
already
have
a
project
that
works
and
just
what
I'm
looking
at
is
a
very
simple
static
site
that
I've
made
with
Hugo,
and
it's
deployed
to
get
lab
pages,
which
you
can
find
pages
down
here
in
the
settings,
and
you
can
also
see
this
is
the
URL
for
my
pages.
A
So
if
I
click
on
this,
it's
going
to
take
me
to
my
hugo
page,
which
is
hosted
here
on
get
lab
pages.
And
so
the
reason
that
I
went
to
this
project
is
because,
let's
say,
I'm
browsing
get
lab
projects
which
you
can
do
here
under
explore
projects
and
I,
see
Hugo
and
I.
Think
that's
a
really
cool
project.
I'd
love
to
to
fork
that
to
build
my
own
static
site.
A
Now
one
thing
about
forking
is:
if
you
go
into
settings
general
and
then
you
scroll
the
bottom
to
advanced,
you
can
see
that
this
is
a
fork
and
it
has
a
fork
relationship
and
if
I
wanted
to
I
could
remove
that
fork
relationship
if
I
click
here
I'll
get
a
pop-up
I'd
have
to
actually
type
in
some
text
to
confirm
that
I
wanted
to
remove
that
fork
relationship
because
it
cannot
be
reestablished.
I
could
do
that
I'm
not
going
to
do
that.
You'd
get
the
same
pop-up.
A
If
you
wanted
to
remove
the
project
and
then
also
a
cool
feature
that
we
have
is
when
you
remove
a
project,
it
just
places
it
into
a
read-only
State
for
a
given
amount
of
days.
So
it's
like
a
soft
delete
and
you
can
restore
it
in
case
you
didn't
actually
mean
to,
but
you
have
to
be
very
intentional
to
a
project
because
there's
so
many
things
that
you
have
to
do
in
order
to
do
that.
A
So
I'm
just
going
to
go
ahead
and
kick
that
off
and
run
this
job,
which
is
called
pages
here
and
I
can
see
it
doing
here
if
you
care,
but
since
that's
outside
the
scope
of
the
Deaf
section,
we'll
hop
back
into
dev
section
things
now
going
back
into
the
repository,
you
can
see
a
bunch
of
different
things.
Obviously
we
have
the
files.
You
can
also
view
the
commits
and
now
remember
this
is
a
fork
so
I'm
going
to
get
all
the
commits
from
the
fork
as
well.
A
All
of
the
branches
you
can
see
that
looks
like
there's
one
open
branch,
other
than
master
master.
Has
these
tags,
it's
the
default
branch
and
it's
also
protected
and
a
protected
branch
inside
of
gitlab
affords
you
certain
cautions
and
certain
guarantees
on
who
can
do
things
to
that
branch?
You
can
set
up
merge,
request
approvals,
that
people
can
only
merge
that
to
that
branch
and
it's
a
nice
way
to
essentially
keep
your
master
a
little
bit
cleaner
and
obviously
a
little
bit
more
control
over
who
can
do
things
with
that
particular
branch?
A
A
A
A
Our
issue
description
box
is
essentially
a
markdown
editor,
so
you
can
see
here
that
this
is
essentially
markdown
and
then
you
can
click
here
to
see
the
rendered
markdown.
So
if
you're
familiar
with
with
markdown,
all
of
the
basics
are
here
and
if
you
need
help,
you
can
also
use
the
buttons
here.
If
you
wanted
to
insert
a
link,
make
a
quote
italicize
or
bold
text
as
well.
A
A
And
I
could
also
edit
the
assignee
if
I
wanted
to.
You
can
have
multiple
assignees
as
well,
and
then
these
other
sidebar
things
will
come
back
to
you
after
I
make
them.
So,
let's
talk
about
labels
for
a
second
labels
are
a
really
powerful
construct
inside
of
get
loud.
That
lets
you
essentially
tag
issues
and
merge
requests,
and
then
you
can
filter,
sort
and
then
modify
boards
based
off
of
those
labels
as
well,
and
so
we'll
get
into
that.
So,
let's
make
a
label.
We
have
two
types
of
labels.
A
We
have
just
general
labels
that
are
used
for
tagging
and
then
we
have
scoped
labels,
which
essentially
are
a
key
value
pair
that
are
explicit
in
terms
of
the
the
key
the
pair
that
you
link
to
the
key
and
I'll
talk
about
both
of
these
in
a
second.
So
let's
just
make
a
label,
it
says
feature,
so
we
want
new
features
and
this
label
is
used
for
new
features.
I
can
give
it
a
color
if
I
want,
but
I'm
just
gonna
go
ahead
and
create
that
label.
A
A
Create
label,
and
essentially
what
these
labels
are,
is
exclusive
labels.
So
if
I
apply
a
priority-one
label
to
an
issue
and
then
later
I
change
or
I
add
the
priority
to
label,
it
will
automatically
remove
the
priority
one.
So
you
can
never
have
more
than
one
scope
to
label
on
an
issue,
and
so
let's
go
back
to
our
issue
and
apply
some
labels
and
actually,
let's
make
these
a
different
color.
A
A
And
you
can
see
that
this
the
issue
description
comments.
The
system
notes
appeared
automatically
because
I
added
these
labels.
Now,
let's
say
we,
we
determine
offline
that
this
is
actually
a
priority
to
feature
so
I'm
gonna
apply
the
priority
to
you
can
see
it
automatically
removed
the
priority.
One
label
and
I
can
never
have
both
of
those
labels
applied
to
this
issue.
At
the
same
time,
I
can
also
give
the
issue
a
weight.
Let's
say:
I
give
it
a
weights
of
three
I
can
lock
the
issue.
I
can
make
it
confidential.
A
A
A
A
It's
going
to
apply
that
label
to
the
card
and
when
you
move
it
from
one
list
to
another,
with
respect
for
them
to
do
to
doing
it's
going
to
remove
one
of
those
and
it's
going
to
add
the
other,
not
sure
why
that
that's
another
thing
we
should
fix.
You
can
see
that
it
actually
has
added
the
labels
over
here,
but
it's
not
showing
up
over
here
and
so
I'm
going
to
try
to
refresh
it
to
see.
If
that
shows
up
again-
and
it
looks
like
it
doesn't.
A
So,
let's
move
it
back
to
to
do
and
you
can
see
that
the
label
did
update
over
here,
but
it
hasn't
updated
on
the
card,
and
so
that's
something
we
should
go
and
address
so
I'm
gonna
move,
maybe
changing
the
color
for
the
background
into
doing
and
changing
the
title
blog
into
to
do.
If
you
click
on
the
white
space
of
a
card,
you
will
pull
in
the
sidebar
of
the
issue
from
the
right,
so
you
can
edit
some
of
the
sidebar
and
then
you
can
also
remove
it
from
the
board.
A
If
you
wanted
to
when
an
issue
gets
closed,
it
goes
off
of
the
off
of
a
board
completely,
and
so,
if
I
drug
this
card
into
this
closed
column,
it
would
actually
close
the
issue,
and
so
that
can
be
really
useful.
If
you're
managing
a
team,
that's
using
Kanban
or
something
along
those
lines.
But
labels
aren't
the
only
things
you
can
actually
do
to
have
board
lists.
A
You
can
have
a
whole
bunch
of
other
board
lists
as
well,
and
so
what
I'm
going
to
do
to
show
that
is
I'm
going
to
just
make
a
new
board
so
I'm
gonna
click
on
the
drop
down
here
and
click
create
new
board
I'm
gonna
say
this:
is
my
assignee
board
time
board
and
this
way,
what
this
will?
Let
me
do
is
it'll.
Let
me
see
all
the
work
that's
assigned
to
the
various
people.
I
have
on
the
project.
A
So
in
this
case
it's
just
me
and
Gabe,
and
so
I'm
gonna
make
a
list
that
can
show
each
of
us
our
work
very
easily,
so
I'm
gonna,
say
okay.
This
is
my
assignee
board
I'm
not
going
to
limit
the
board
scope
right
now,
because
I
want
to
see
all
issues
but
say
if
I
wanted
to
see
just
issues
that
were
key
ones.
For
example,
I
could
limit
the
scope
of
the
board
to
any
issue
that
just
had
this
label,
which
would
just
let
me
see
maybe
issues
that
were
signed
to
gave
in
myself.
A
That
only
were
Priority
One
boards
are
very
flexible
and
customizable.
This
way
so,
please
play
around
with
it
and
let
us
know
if
you
have
any
ideas
or
any
thoughts,
so
I'm
gonna
go
ahead
and
create
this
board.
It's
not
going
to
be
scoped.
So
it's
going
to
show
me
both
of
those
issues
and
what
I'm
going
to
do
is
I'm
going
to
add
a
list.
A
board
list,
I'm
gonna
click
over
here
board
list
and
I'm
I
can
make
list
space
off
of
labels
assignees
or
milestones
now.
A
I
want
to
make
them
based
off
of
a
psyche,
and
so
I
want
to
make
a
list
for
me.
So
you
can
see
I've
made
a
list
for
myself,
and
the
issue
that
is
assigned
to
me
is
automatically
moved
over.
There
I'm
also
going
to
make
a
list
for
Gabe,
and
you
can
see
that
both
of
the
issues
here
moved
over
here
and
so,
unlike
the
last
board
that
we
had
an
issue
can
be
in
multiple
places
on
this
board,
because
it's
an
assignee
board.
A
So
boards
are
very
powerful
to
use
to
just
understand,
signees
they're,
very
powerful,
to
use
to
understand
how
we're
closed.
If
you're
using
like
a
Kanban
methodology-
and
then
you
can
also
use
them
just
to
see
like
directionally
roadmap
from
a
roadmap
perspective,
if
you
wanted
to
make
a
board
by
milestone,
to
see
hey,
what's
in
my
next
release
and
the
release
after
that
and
the
release
after
that,
it's
very
very
easy
to
make
a
board
that
can
show
that.
A
So,
let's
go
into
our
project
and
let's
actually
make
a
change
here.
So
have
this
repository
I've
said:
I
want
to
make
a
few
changes
based
off
of
issues.
How
do
I
actually
do
that?
Well,
we
have
this
really
cool
project,
a
feature
built
into
the
products
called
our
web
IDE
and
if
you're
a
developer,
you
most
likely
use
a
local
IDE.
A
But
if
you
want
to
make
a
very
quick
change
to
code
and,
let's
say
you're
on
the
go
or
you
aren't
at
your
your
workstation,
where
everything's
set
up
our,
we
have
a
really
cool
integration
or
feature
built
into
the
product.
Call
our
web
IDE,
where
you
can
make
changes
and
you
can
commit,
and
you
can
make
an
EM-
are
very
very
quickly
to
make
that
change
back
into
the
master
branch
or
whatever
branching
you
to
go
to
so
over
here
to
the
left.
A
A
Let's
just
go
ahead
and
say:
maybe
there's
multiple
Eric's
working
on
this
blog
again,
so
I
wanted
to
say
Eric
Brinkman,
so
because
this
is
a
markdown.
You
can
also
preview
the
markdown
here
by
clicking
on
this
tab,
but
I've
made
a
change
and
you
can
see
that
there's
a
change
here.
There's
a
change
here,
that's
unstaged
and
not
yet
committed.
A
A
A
To
be
in
the
same
group,
EB
test
group
to
Hugo,
and
so
we're
gonna
go
ahead
and
compare
our
branches
and
do
that
and
similar
to
in
the
issue
description.
We
can
give
this
a
description
of
a
merge
request
which
says:
updates
Eric's
last
name,
because
because
we
have
too
many
on
staff
I'm
going
to
sign
this
to
myself
and
I'll.
Give
this
also
that
feature
and
doing
label.
A
We
have
a
really
neat
feature
called
merge,
request
dependencies,
and
so,
if
there
was
another
merger
quest
that
was
dependent
on
this
one
or
you
could
link
it
here
and
essentially
what
that's
going
to
allow
you
to
do
is
to
map
dependencies
amongst
merge,
requests
and
they'll
prevent
emerged.
If
another
merger
quest
needs
to
be
merged
before
the
merge
request,
you're
looking
at
needs
to
or
can
be
merged,
and
so
it
can
be
a
nice
feature
for
essentially
indicating
dependencies
amongst
changes
to
your
code
base.
A
We
also
have
approval
rules
and
I'm
not
going
to
add
any
rules
here,
but
we
can
specify
the
number
of
approvals
required
and
then
who
actually
can
can
approve,
and
so,
if
I
were
to
click
approval
rules
said
my
rule,
number
of
rules
required
I
could
search
from
a
group
or
a
user
and
then
add
a
rule.
We're
not
going
to
do
that
now
and
then
there's
also
some
merge
options.
A
There's
one
that's
selected
by
default,
which
is
to
delete
the
source
branch
where
the
merge
request
is
accepted
just
to
clean
up
after
yourself
a
little
bit
and
then
to
squash
commit.
So
if
you're
going
to
have
a
lot
of
commits
and
so
I'm
gonna
go
ahead
and
submit
the
merge
request
and
what's
that's
going
to
do?
Is
it's
going
to
actually
create
the
merge
request
for
us
in
the
merge
request
creation
screen?
You
can
see
that
we
have
an
overview
which
contains
the
discussion.
A
We
have
a
commits
tab
which
shows
the
list
of
all
the
commits
in
that
merge
request.
The
pipeline's
that
will
automatically
run
when
@mr
or
a
commit
happens
against
an
NMR
and
then
also
the
changes.
So
this
is
your
diff
tab,
more
or
less,
and
so
you
can
see
here.
That's
we've,
we've
made
a
change,
and
one
thing
I
want
to
highlight
here
is
that
you
can
comment
on
a
line
on
a
disk.
So
if
someone's
reviewing
this
in
a
code
review
scenario
say
it
looks
good
to
me,
you
can
add
that
comment
now.
A
You
can
also
make
a
change
very
quickly
to
the
actual
code
itself
by
using
a
feature
called
insert
suggestions.
So
there's
a
little
button
here
called
insert
suggestions
and
if
you
do
that,
it'll
copy
the
line
from
the
diff
over
and
let's
say,
for
example,
I-
actually
use
the
wrong
Eric.
So
we
have
another
Eric
on
our
team.
His
last
name
is
sugar.
Let's
say
Eric
sugar
was
actually
the
one
who's
supposed
to
write
this
and
so
I've
changed
his
name.
I'm
gonna.
Add
this
comment.
Now.
A
What
this
comments
going
to
do
is
just
gonna
say:
hey
I,
think
this
is
a
change
you
should
make
on
your
diff
and
if
you
wanted
to,
you
can
actually
apply
it.
A
suggestion
right
from
the
diff
as
well
I'm
gonna
do
that
by
clicking
this
apply
suggestion
button,
it's
going
to
give
it
a
little
badge
that
says
it's
applied,
and
it's
also
going
to
tell
me
that
I
just
changed
this
in
version
2
of
the
diff,
and
so
it's
a
really
neat
feature
for
making
very
small
changes
and
tweaks
right
in
the
diff
view.
A
A
A
A
A
That
should
be
picked
up
pretty
soon,
we'll
come
back
and
check
on
that
in
a
little
bit,
but
all
in
all
that
is
essentially
a
run-through
of
the
dev
section
capabilities.
There's
one
other
feature:
I
want
to
highlight
as
well,
which
is
our
design
management
capabilities.
So
let's
say
that
we
went
back
to
this
issue
here,
where
we
were
changing
the
color
of
the
blog
background.
We
have
this
tab
right
here
in
the
middle
called
designs,
and
this
is
a
place
where
for
designers
to
communicate
and
collaborate
with
their
development
teams,
I
can
click.
A
Maybe
I
love
this
color
of
translucent
orange
and
say
I
gave
I
love
the
look
of
this
translucent
orange.
It
reminds
me
of
the
old
Macs
from
was
that
the
early
2000s
I
think
and
I
could
comment
on
this,
and
you
can
see
comet
number
one
point
of
interest
comment
here
and
then
I
could
also
add
other
comments
around
the
image.
If
I
wanted
to
you
can
delete
the
image
and
I
can
also
download
the
image
as
well.
A
A
A
We
will
check
on
that.
Okay,
and
you
can
also
see
that
when
I
added
this
design
and
I
started
a
discussion
here
that
it
was
provided
as
systemness
out
to
the
rest
of
the
issue
description.
So
a
really
cool
feature
that
the
team's
been
working
on
I'm
excited
to
bring
designers
alongside
DevOps
workflow.
A
A
A
So
I
think
that's
one
thing.
The
other
thing
is
I
was
a
little
bit
surprised
to
see
that
the
labels
were
not
updating
when
you
drugged
them.
Oh
now,
it
seems
to
work,
but
it
doesn't
work.
You
can
see.
Oh
no!
This
is
an
assigning
board.
Sorry,
let's
go
back
to.
Let's
go
back
to
our
development
board.
A
Yes,
these
labels
don't
show
up
here
curious
if
it's
actually
works.
If
I
were
to
add
another
list
for
future,
you
can
see.
There's
just
there's
label
inconsistency
here
this
this
issue
has
the
doing
label.
It
clearly
does
not
have
the
doing
label
on
the
card
and
so
on
and
so
forth.
So
labeling
consistency.
A
So
that's
something
to
look
into
so
all
in
all
I
think
it's
a
successful
Walker
wasn't
as
polished
as
I,
wanted
it
to
be
probably
stumbled
a
few
more
times
than
I
wanted
to,
but
I
think
the
point
of
doing
these
is
to
take
a
workflow
and
to
end
and
see
how
easy
or
hard
is
it
to
do
and
I
think
there's
a
fair
amount
of
polish
for
us
to
make
this
better.
So
I
hope
you
all
enjoyed
it.
I
know
it
was
rather
long.