►
From YouTube: Intro to GitLab Webinar - AMER Time Zone Webinar
Description
Are you new to GitLab? Watch this webinar to learn more about what GitLab is, how it benefits you, and the recommended workflow to allow you to get the most out of the platform.
A
A
All
right,
let's
go
ahead
and
jump
in.
Thank
you
again
for
for
joining
us.
We're
we're
glad
to
have
you
on
with
us
today,
as
you
can
see
on
the
screen,
we're
going
to
be
going
through
introduction
to
git
lab
so
looking
forward
to
going
through
that
content
with
all
of
you
before
we
do
I
just
wanted
to
go
through
a
couple
of
housekeeping
items.
A
Additionally,
if
you
have
any
questions
that
come
up
throughout
the
session,
please
feel
free
to
put
those
in
the
Q
a
portion
of
your
Zoom
window,
and
we
will
be
able
to
answer
those
as
we
go
throughout
the
session
today
and
we'll
have
a
little
bit
of
time
at
the
end
for
Chris.
To
answer
some
questions
as
well
and
with
that
I'll
I
will
hand
it
over
to
Chris.
Who
is
a
customer
success
engineer
in
our
customer
success
team.
Looking
forward
to
hearing
from
him
today.
B
Secondly,
we'll
also
go
through
the
recommended
git
lab
flow
for
a
future
Branch
development
workflow.
This
is
key
to
utilizing
all
the
features
in
the
gitlab
devops
platform,
so
I
want
to
make
sure
that
we
tackle
that
and
then
just
to
let
you
know,
we
do
have
some
upcoming
webinars
that
we'll
be
presenting
into
the
future
that
include
intro
to
CI
CD
Advanced,
the
ICD,
as
well
as
Del
psychops
and
compliance.
B
B
All
right
so
before
we
jump
into
some
more
of
the
more
details
here,
I
want
to
give
you
an
overview
of
gitlab
and
gitlab
is
the
first
and
only
true
devops
platform.
It's
a
single
application
with
one
user
interface,
a
unified
data
store,
one
permission
model
and
security
embedded
within
the
devops
lifecycle
in
a
single
application.
B
Every
team
in
your
organization
can
collaborate
in
a
single
solution
to
manage
the
end-to-end
development
lifecycle,
delivering
more
value
faster,
increasing
visibility,
quality
and
security,
while
removing
context,
switching
and
non-value
generating
tasks.
So
this
is
just
a
good
overview
of
all
the
kind
of
capabilities
that
you
can
get
within
gitlab
as
the
one
devops
platform
as
a
single
application.
B
So
you
might
ask
you
know
why
do
so?
Many
organizations
use
gitlab
and
what
problem
is
it
solving
and
really
here
we're
moving
we're
helping
teams
move
from
sequential
devops,
which
is,
on
the
left
hand,
side
here
to
concurrent
devsecops,
which
is
implemented
by
leveraging
all
of
the
features
Within
gitlab.
B
B
So
these
two
lines
here
represent
so
this
line
here
and
then
this
line
up
here
represent
two
branches,
but
all
work
being
done
on
the
feature
branch.
So,
as
you,
you
know,
organizer
work
through
epics
and
Milestones
and
issues
and
then
assign
an
issue
to
a
developer.
That
developer
will
create
a
merge
request
and
create
a
new
feature
branch
and
for.
B
It
goes
through
that
same
automated,
build
and
test
process
and
security
scanning
and
finally
reaches
the
collaboration
review
again.
Once
everything's
passed
and
everything's
approved,
it
can
then
be
deployed,
so
merge
is
accepted,
so
it's
merged
that
feature
branch
has
merged
back
into
the
main
deployment
Branch.
It's
released
and
deployed
to
your
production
environment
along
the
way
you
can
utilize
things
like
the
the
review
app
functionality.
B
We
don't
go
through
that
today,
here
in
today's
webinar,
but
if
you're
interested
in
the
review
app
functionality
we'll
touch
on
that
within
our
intro
to
CI
CD
as
well
as
advanced
CI,
CD
webinars,
so
keep
an
eye
out
on
those.
If
you
want
to
take
advantage
of
some
more
of
the
advanced
functionality
within
the
Pipelines.
A
B
Branch
and
then
merging
it
back
into
your
main
deployment
Branch,
so
I'll
get
you
know,
allows
a
wide
variety
of
branching
strategies
and
workloads.
You
know
many
organizations
end
up
with
workflows
that
are
too
complicated
and
not
clearly
defined
or
not
integrated
with
issue
tracking
systems.
So
if
you're
utilizing
gitlab
flow,
you're
you're
following
our
clearly
defined
set
of
best
practices,
so
what
that
does?
B
So
we
do
recommend
the
devops,
for
we
do
recommend
devops
teams
to
follow
the
gitlab
flow
process,
while
using
gitlab
capabilities
in
this
concurrent
development
lifecycle
and
as
a
reminder,
the
klab
application
is
really
based
around
a
feature
Branch
based
workflow.
So
all
developers
will
work
within
a
single
project
and
create
feature
branches
in
that
same
project
and
in
the
merger
Quest
that
becomes
the
core
and
primary
collaboration
tool
of
the
product
to
allow
you
to
push
the
code
to
that
feature.
Branch
perform
your
automated
build
and
test
process.
B
B
B
These
are
all
the
terminology
that
you
would
use
to
say,
for
example,
Define,
a
project
which
is
the
core
building
block
where
work
is
organized,
managed
tracked
and
delivered
to
help
the
team
collaborate
and
plan
work
in
the
form
of
issues.
So
all
of
your
issues
are
found
in
gitlab
projects,
if
you're
using
other
devops
tools,
a
project
could
also
be
known
as
a
repository
and
then
a
project
as
part
of
a
group.
B
Next
up
we
have
the
issue.
A
issue
is
essentially
part
of
a
project,
as
I
mentioned,
it's
the
fundamental
planning
object
where
your
team
will
document
the
use
case
of
a
specific
feature
and
the
title
and
the
description,
and
in
the
description
you
will
discuss
the
approach
estimate.
The
size
and
effort
of.
B
That
needs
to
be
done
using
the
issue,
weight
and
actually
tracking
the
the
time
spent
for
for
completing
that
issue.
You
can
assign
issues
to
any
number
of
individuals
on
the
team.
It
could
be
one
individual
or
multiple
individuals
and
that's
really,
where
you're
going
to
be
tracking
the
progress
for
the
work
that
needs
to
be
completed.
B
You
may
want
to
organize
them
in
an
epic
and
git
lab,
and
so
you
can
organize
these
by
theme,
whether
that's
related
to
an
Initiative
for
the
current
quarter
or
a
specific
capability
focusing
on
say,
like
the
user
experience
or
back-end
functionality,
you
can
have
an
epic
that
would
help
you
organize
all
those
issues
that
relate
to
one
another,
and
that
would
help
you
achieve
that
particular
goal.
That's
outlined
in
the
Epic
next.
B
Merger
Quest,
so,
as
we
mentioned
in
the
previous
slide
here
on
the
recommended
process,
the
merge
request
is
essentially
your
primary
collaboration
tool
where
feature
branches
are
associated
there
and
where
developers
are
primarily
doing
their
work
and
collaborating
with
the
team
to
have
them
review
and
have
them
approve
the
work
once
it's
completed
so
this
captures,
you
know
the
merge
request
can
capture
the
design
and
that's
being
changed.
You
know
any
implementation
details,
so
code
changes
within
the
software
itself.
B
You
know
discussions
within
specific
lines
of
code
or
just
generally
discussions
around
the
changes
that
are
being
made
and
the
approval
process,
as
well
as
the
testing
the
automated
build
and
testing
that
happens,
as
well
as
the
security
scans
and
other
tools.
This
may
be
known
as
the
pull
request,
but
here
in
gitlab
it's
called
a
merge
request.
B
Next,
we
have
the
gitlab
label,
and
labels
are
a
way
for
you
to
tag
and
track
your
work
for
projects
and
groups
and
Associate
different
issues
with
different
initiatives
may
also
help
you
prioritize
different
things,
so
you
can
create
labels
that
correspond
to
different
priorities
that
you
want
to
assign
to
your
issues.
You
know
priority
one
priority
two
priority
three
priority:
four,
so
those
labels
can
help
you
organize,
what's
important
to
you
and
to
your
team
boards.
B
These
boards
are
a
visual
listing
of
projects
and
issues
that
are
useful
for
teams
to
manage
their
backlog
of
work,
helping
you
prioritize
items
and
move
issues
to
the
team
or
specific
stage
in
the
project,
so
we'll
go
through
through
this
a
little
bit
later
and
the
slides
here
where
I
can
demonstrate
to
you
how
to
utilize
boards
to
really
help
you
organize
the
backlog
of
work
or
help.
You
apply
labels
automatically.
B
Next,
we
have
the
Milestone
and
iteration
Milestone
iterations
are
used
to
track
a
Sprint
or
specific
deliverable,
and
it
helps
you
organize
codes.
It
code,
your
code
issues
and
merge
requests
into
a
cohesive
group.
For
example,
we
use
the
Milestone
feature
at
gitlab
to
track
our
monthly
releases
that
happen
on
the
22nd
of
each
month.
And
so,
if
you
look
at
the
the
gitlab
project,
which
we'll
go
through
in
a
few
slides
here,
you
can
see
that
there's
Milestones
that
are
created
for
every
gitlab
release,
that's
being
created.
B
B
Projects
are
housed
within
groups,
so
you
can
see
here,
there's
a
top
level
group,
and
then
you
have
a
project
right
underneath
that,
but
groups
can
also
have
any
number
of
subgroups
to
help
you
better
organize
your
projects
based
on
teams
within
your
organization
or
different
parts
of
your
software
applications
that
you're
building.
So,
for
example,
you
may
have
a
top
level
group
for
your
company
or
organization,
but
you
may
have
subgroups
to
split
up
your
projects
based
on
the
type
of
work
that
they're
doing
so.
B
If
they're
doing
mobile
applications,
you
may
have
a
subgroup
for
mobile
applications.
You
may
even
split
that
out
even
further
to
have
subgroups
for
your
iOS
team
and
your
Android
team,
for
example,
and
then
you
may
have
another
subgroup
for
your
back
end
team
and
your
front-end
team
and
then
the
different
projects
that
are
associated
with
those
with
those
teams
and
so
with
how
things
are
organized.
You
know
when
you
add
team
members
to
say
a
top
level
group
permissions
are
actually
inherited
from
the
top
level
group.
B
If
you
want
have,
if
you
want
to
have
your
entire
team
added
at
the
top
level
group
labels
and
Milestones
created
the
top
group
level,
are
available
to
all
of
your
subgroups
and
projects
so
to
kind
of
better
help.
You
organize
your
work.
You
may
think
about
creating
all
of
the
labels
and
Milestones
that
your
groups
may
want
to
leverage
at
the
top
level
group.
So
that
way,
you
don't
need
to
recreate
them
individually
at
specific
projects
or
even
specific
subgroups.
They
can
all
be
inherited
from
the
top
level
group.
B
Next,
you
know,
as
we
kind
of
showed
you
in
the
gitlab
flow
slide.
A
few
slides
ago.
We
took
you
through
an
example,
workflow
of
a
feature
branch
and
all
the
work
that's
being
done
within
gitlab,
but
in
this
example,
we'll
show
you
really
more
specifically
through
all
the
way
from
creating
And
discussing
a
new
issue
and
deploying
to
production,
more
granularly.
So
in.
A
B
A
team
member
creates
an
issue
inside
gitlab
for
a
new
feature
that
they'll
be
implementing
the
team.
Member
applies
to
this.
The
label
discussion
to
the
issue
and
various
team
members
discuss
the
new
feature
by
entering
comments
into
the
issue.
The
issue
will
now
appear
on
the
Project's
issue
board
in
the
discussion
list
and
other
labels
for
this
project
could
include
back-end,
front-end
working
on
staging
ready
and
production.
B
The
assigned
developer
starts,
writing
the
code
and
assigns
the
issue
to
themselves
and
changes
the
label
to
working
on
next
comes
the
commit
and
merge
requests,
so
the
developer
creates
commits
and
the
developer
pushes
their
commits
to
a
feature.
Branch
and
the
developer
creates
a
merge
requests.
Then
the
back
end
team
removes
the
back
end
and
working
on
labels
and
adds
the
label
front
end.
B
That
then,
generates
the
next
stage
here,
deploying
to
staging
environment
where
the
front-end
developer
starts
working
on
the
issue,
adding
the
label
working
on
and
assigning
the
issue
to
themselves
and
after
the
code
review
is
complete,
the
code
is
deployed
to
the
staging
environment
and
the
team
removes
the
labels
and
adds
a
staging
label.
So
after
the
successful
implementation
of
the
application
in
the
staging
environment,
the
team
removes
the
staging
label
and
adds
the
label
ready.
B
So
once
it's
in
the
ready
stage,
other
teams
prepare
the
technical
documentation
and
the
marketing
campaign
each
adding
their
label
stocks
and
marketing
and,
as
each
team
is
done,
they
remove
their
labels
and
the
last
team.
That's
done
removes
the
ready
label
and
adds
the
production
label,
and
then
that
means
we're
ready
to
move
to
production.
So
with
a
move
to
production,
the
release
team,
member
merges
the
merge
request
and
the
feature
is
deployed
to
the
production
environment
and
the
release
team
member
closes
the
issue.
B
B
So
here
you
can
see
we're
in
the
top
level
group,
so
I've
taken
a
screenshot
here
of
the
top
level
group
gitlab.org
on
gitlab.com,
and
you
can
see
all
the
subgroups
and
projects
underneath
this
group
s
within
this
top
level
group
have
the
three
dots
icon
here
so
with
the
five
minute
production
app.
This
is
a
subgroup
and
then
projects
have
this
book
icon
here.
B
B
B
So
in
Epic,
as
you
might
remember,
it's
a
collection
of
related
issues
across
different
groups
and
projects
to
help
you
organize
by
a
specific
theme.
So,
as
you
can
see
here,
you
can
search
for
epics
using
specific
keywords
or
specifying
a
specific
label.
So
here
I'm
looking
for
all
epics
that
are
not
confidential.
What
a
label
of
priority
three
and
once
I've
entered
in
that
search.
Query:
I've,
filtered
it
down
to
the
sources
for
external
dependencies,
epic,
as
well
as
follow-up
for
dependencies
that
are
IO
integration,
Epic.
B
So
an
epic
it
could
be
a
portfolio
initiative
or
investment,
a
specific
capability
or
feature
or
just
a
large
story.
You
want
to
utilize
an
epic
to
capture
its
description
or
business
case
here
in
the
description
field
and
any
data,
or
that's
pertinent,
to
describe
this
large
body
of
work
that
needs
to
be
completed.
So
here
we've
got
the
license:
compliance
category
Vision,
epic,
so
in
an
epic
you've
got
a
title
and
then
a
body
or
description
that
uses
markdown
for
you
to
kind
of
format
with
a
bulleted
list.
B
As
in
Additionally,
you
can
apply
different
labels
to
help
you
organize
your
epics.
As
I
mentioned,
you
can
create
those
labels
at
the
top
level
group
and
those
labels
can
then
be
available
to
your
subgroups
and
to
the
epics
and
issues
that
need
to
be
organized.
So
here
we've
organized
this
epic
under
the
devops,
secure
scoped
label
and
some
other
labels
here
as
well,
and
you
can
actually
click
these
labels
to
view
a
list
of
all
epics
or
all
everything
that
is
captured.
B
B
So
you
can
see
here.
These
are
all
hierarchical
and
dynamic,
so
you
can
expand
and
collapse
these
different
character
for
the
sub
child
epics,
and
then
you
can
start
to
see
any
nested
child
epics
within
the
Epic
itself
and
then
finally,
the
issues
as
well.
So
you
can
see
that
epics
are
designated
by
a
stack
of
papers.
For
example,
this
license
compliance
moving
from
minimal
to
viable
and
in
there
you've
got
another
sub.
A
child.
Epic
called
replace,
license.
B
B
Features
are
only
available
in
the
ultimate
tier
of
gitlab,
so
child
epics
are
only
available
on
Ultimate.
If
you're
a
premium
customer,
then
you'll
only
be
able
to
see
issues
that
are
directly
linked
to
the
Epic,
but
not
necessarily
creating
child
epics
that
are
nested
within
an
epic,
and
then
you
may
also
see
that
we've
got
a
health
status
as
well.
So
these
green,
yellow
and
red
numbers
at
the
top
of
an
epic
up
here,
as
well
as
individually
within
child
epics,
those
designate.
How
many
issues
that
are
on
track
need
attention
or
at
risk.
B
B
This
view
shows
all
the
issues
and
all
of
the
projects
under
this
group
so
similar
to
The
Epic
view
this
list
can
be
filtered
by
keyword
or
by
relevant
metadata,
such
as
the
auditor,
assignee,
Milestone
or
label,
and
you
can
see
information
about
each
issue
in
the
list,
including
the
labels,
the
assignees.
So
you
can
see
the
assignees
here
on
the
right
hand,
side
with
the
their
Avatar
the.
A
B
B
So
these
different
search
filters
can
be
combined
with
other
search
parameters,
including
who
the
author
is,
who
the
assignee
is
and
specific
keyword,
searches
as
well
to
find
any
text,
that's
within
a
description
or
title
for
example.
So
as
you
add
additional
search
parameters
or
adjust
the
Sorting,
the
URL
in
your
browser
will
actually
be
updated
with
the
appropriate
query
string
parameters.
B
So
you
can
actually
save
the
same
exact
query
and
bookmark
it
or
share
that
that
same
query
with
someone
else
by
copying
pasting
into
a
slack
message,
an
email
or
even
adding
to
another
gitlab
issue
to
get
folks
to
the
right
list
of
issues,
that's
filtered
by
a
specific
label
or
milestone.
For
example,.
B
B
So
you
can
see
as
I'm
scrolling
here
you
can
see
all
the
different
metadata
here,
but
we'll
start
here
at
the
at
the
top
of
the
issue
right
above
the
the
headline
or
the
title,
you
can
see
the
status
of
the
issue,
whether
it's
open
or
closed,
when
the
issue
was
created.
So
this
is
kind
of
like
a
relative
date,
but
if
you
hover
over
it,
you
can
actually
see
the
exact
date
and
time
who
the
original
author
of
the
issue
is
and
then
their
specific
role
in
the
project
and.
B
B
B
This
is
what
we're
using
to
track
what
issues
are
assigned
to
a
specific
release
of
gitlab
that
we're
wanting
it
to
be
included
on
the
iteration
that
the
issue
belongs
to
so,
if
you're
tracking,
the
work
specifically
in
a
specific
Sprint
that
specific
time
say,
a
two-week
Sprint
and
you'll
see
that
assigned
there.
The
issue
8,
which
is
an
integer,
to
show
the
relative
to
the
difficulty
for
completing
this
issue.
B
So
these
are
all
whole
positive
numbers
that
you
would
be
assigning
in
the
issue
weight
and
some
common
patterns
that
you
would
utilize
for
the
issue.
Weight
are
the
Fibonacci
sequence
or
whole
numbers
that
you've
kind
of
aligned
to
t-shirt
sizes
that
you
might
have
used
in
previous
devops
tools.
So,
if
you're,
using
small,
medium
large,
for
example,
you
may
have
say
like
a
weight
of
one
for
small
three
to
medium
and
five
for
large,
for
example,
you
also
have
the
due
date
as
well
as
some
time
tracking.
B
B
And
you
would
have
them
all
on
their
own
lines
and
you
could
essentially
set
the
time
estimate
so
estimated
time
that
would
be
needed
to
complete
the
issue
as
well.
As
you
know,
capturing
any
time
that's
spent
within
the
issue.
You
know
as
you
work
on
it
and
then.
Finally,
as
I
mentioned
before,
with
the
health
status
feature
on
the
epics
better,
that's
kind
of
bubbled
up
to
the
epics
view
you
have,
you
can
assign
the
health
status
which
is
on
track,
needs
attention
and
at
risk.
B
A
A
B
A
B
I'm
not
sure
why
that's
not
showing
up
here
with
each
comment.
You
can
mention
different
folks
here
and
you
could
have
threaded
conversations
and
mention
other
users
to
bring
their
attention
and
when
you
mention
somebody
else
that
will
send
them
an
email
notification
and
request
action
on
an
issue.
So
you
may
ask
somebody
to
you:
may
provide
some
feedback
to
someone
or
ask
them
to
ask
them
for
their
thoughts,
and
each
issue
or
comment
can
be
reacted
to
be
an
emoji.
So
you
know,
rather
than
kind
of
writing
out
a
whole
response.
B
You
can
click
this
button
here
and
give
a
thumbs
up
or
plus
one
as
well
as
the
issue
itself
could
have
Emoji
reactions
as
well.
So
we
use
this
at
gitlab
to
track
support
from
our
team
members
and
community
members
and
our
customers
on
issues
that
have
the
most
upvotes
or
thumbs
up
to
help
influence
our
product
prioritization.
So.
B
B
B
Issues,
you
also
have
the
ability
just
to
show
all
those
related
issues
as
well
as
related
merger
quests.
So
any
work,
that's
being
done.
That's
contributing
to
the
completion
of
that
issue.
You'll
see
that
in
the
list
there
related
merge
requests
and
then,
on
the
right
hand,
side
here.
These
are
all
the
the
discussions
that
are
happening
within
the
issue,
so
comments
that
are
happening.
Conversations
that
relate
to
the
work
that's
being
done
to
achieve
that
common
goal.
B
B
You
can
have
columns
in
the
in
the
in
the
boards
based
on
labels
and
Milestones
and
assignees,
and
more
so
here
you
can
see
that
we've
got
a
different
lists
within
an
issue
board.
That's
assigned
to
the
scope
level,
priority
critical
and
priority
High
and,
as
you
move,
issues
dragging
and
dropping
issues
between
one
list
to.
B
Automatically
assigning
that
label
to
that
issue,
so
it's
an
easy
way
for
you
to
triage
and
move
your
issues
across
a
specific
workload
that
you've
defined
through
your
labels
and
up
here
you
have
a
drop
down
menu
where
you
can
create
multiple
boards
and
select
different
boards.
For
you
to
kind
of
switch
between
those
different
workflows,
you
could
have
a
workflow
for
your
triage
of
defining
priority.
B
B
Next
I
want
to
go
ahead
and
take
you
through
a
tour
of
the
merger
Quest.
So
with
merge
request,
you
get
a
complete
view
of
all
aspects
of
the
change
being
made
to
the
code
base.
You
can
see
the
latest
pipeline
progress
and
you
can
review
and
approve
the
changes
you
can
review.
The
security
scan
results
all
in
one
place.
Additionally,
gitlab
makes
it
easy
to
start
and
track
progress
of
a
code
review.
B
B
Cicd
as
well
as
advanced
CI
CD
in
gitlab,
but
at
its
core
CI
CD
in
gitlab,
is
defined
as
continuous
integration
and
continuous
delivery
or
deployment
and
gitlab
CI
CD
allows
for
built-in
automated
builds
and
tests
to
be
run
on
your
code
as
you
make
those
changes.
So,
as
we
mentioned
in
that
gitlab
flow
as
you
create
those
feature
branches
you're
going
to
be
triggering
the
gitlab
CI
CD
pipeline
to
create
those
automated
builds
and
testing
your
software
and
scanning.
A
B
Security
vulnerabilities,
as
you
make
those
changes
and
with
gitlab
cicd,
are
encouraging
collaboration
across
all
departments
in
that
merge
request
and
making
code
creation
and
management
easy,
as
well
as
providing
so
polling
specific
benefits
that
I've
outlined
here
so
with
CI
contingency
integration.
It
allows
you
for
early
error,
detection,
reduced
integration
problems
and
increasing
your
team
speed
and.
B
A
B
A
B
B
So
with
labels,
as
I
mentioned,
you
can
create
labels
at
the
group
level.
This
can
be
filtered
by
a
keyword
to
find
specific
or
more
relevant
labels
at
the
group
level.
So,
as
you
create
more
labels
over
time,
it
can
get
a
little
unwieldy
to
go
through
the
entire
labels
list,
so
you
can
use
the
search
functionality
to
find
the
specific
labels
that
you
want
to
edit
or
view
all
the
issues
that
are
related
to
them.
B
Pair
for
your
labels,
so
the
name
is
priority
and
the
value
is
one
so
that
way,
when
you
apply
these
labels
to
an
issue
or
an
epic,
only
one
of
these
labels
can
be
applied
at
a
time.
So
you
can
only
have
an
issue
or
an
epic
with
a
party
one
label
and
if
say
the
priority,
changes
for
that
issue
or
epic,
and
you
apply
the
priority.
Two
label
that
party
one
label
will
automatically
be
removed
and
party
two
would
be
applied.
B
Foreign
s
are
a
way
to
group
issues
and
merge
requests
together
in
a
block
of
time.
Milestones
have
a
defined
starting
and
an
end
time,
and
it
can
include
any
number
of
issues
and
merge
requests.
So
here
you
can
see
all
the
milestones
for
gitlab.org
in
the
gitlab
project
and
any
Milestones
created
for
those
projects
in
the
group.
B
A
B
We've
got
again
as
I
mentioned
here
at
gitlab:
we've
aligned
our
monthly
releases
to
a
milestone,
so
we've
got
15.1
and
15.2,
for
example,
and
so
when
you
look
at
these
milestones
in
this
Milestones
listing
page,
you
get
a
summary
view
of
the
number
of
issues
and
merge
requests
in
the
Milestone
and
how
far
along
that
Milestone
is.
So
you
could
drill
into
these
to
see
a
burn
down,
burn
up
chart
associated
with
the
milestone.
B
System
navigation
tips
to
help
you
get
around
in
gitlab,
so
there's
lots
of
ways
to
navigate
in
gitlab.
On
the
left
hand,
side
you
can
easily
switch
to
different
to
view
different
types
of
data
within
the
group
or
project
that
you're
currently
viewing
and
at
the
top.
You
have
breadcrumbs
that
show
you
where
you
are
in
the
group
and
project
hierarchy
at
the
very
top.
You
can
see
that
whenever
you
change
views
in
gitlab,
the
URL
actually
changes
as
well.
B
B
B
All
right
so
that
concludes
all
the
different
capabilities
that
I
wanted
to
kind
of
share
with
you
in
today's
introduction
to
gitlab.
I
also
wanted
to
kind
of
share
with
you,
some
additional
key
trainings
for
teams
that
are
getting
started
with
gitlab.
So
you
do
have
a
Professional
Services
team
here
at
gitlab,
and
we
have
several
trainings
to
offer
you
for
for
any
any
team.
That's
getting
started,
so
each
training
allows
for
up
to
12
students
from
an
organization
and
to
see
our
current
pricing.
B
Please
visit
our
catalog
page,
that's
linked
here
below
and
we'll
share
this
with
you
after
the
webinar
and
just
to
kind
of
recap,
some
of
the
the
concepts
or
topics
that
we'll
be
covering
in
all
these
trainings.
We
have
the
git
live
with
get
get
Basics
training
which
covers
what
gitlab
does
why
devops
teams
use
it
and
how
it
works
with
Git.
B
B
So
if
you
need
just
a
migration
services
and
not
the
training,
we
also
offer
that
as
well,
and
you
might
consider
a
professional
services-led
migration
if
you're
moving
hundreds
or
thousands
of
repos
into
kitlab
or
you're,
moving
from
a
self-managed
gitlab
instance
to
our
SAS,
offering
just
to
maintain
some
data
integrity,
we
can
share
additional
benefits
documented
in
our
handbook
in
in
the
documentation.
After
the
call
again
I
appreciate
your
time
here.
We've
got
a
little
bit
of
extra
time
here,
just
to
tackle
some
q,
a.
A
Awesome
thanks
Chris
I
I
also
just
opened
up
a
feedback
poll,
so
I
would
love
to
get
your
feedback
from
today's
session.
Just
a
couple
of
quick
questions.
There
should
only
take
a
minute
or
so
and
with
that
we
will
jump
into
some
questions.
We
have
had
a
few
come
in,
so
I'll
just
kind
of
go
through
those
in
the
few
minutes
we
have
left
here
first
question:
I'm
a
self-managed
user
of
git
lab
and
started
creating
projects
in
different
top
level
groups.
B
Great
question
so,
as
I
mentioned
before
you
know,
with
the
gitlab
hierarchy,
you
know
you
essentially
want
to
have
you
know
single
top
level
group
and
subgroups
within
them
to
organize
all
of
your
projects
and
issues,
and
so,
if
you've
started
creating
different
projects
and
different
top
level
groups,
you've
kind
of
broken
that
hierarchy
that
you
know
a
top
level
group
is
aware
of.
So
if
you
were
to
create
an
epic
at
that
top
level
group-
and
you
want
to
add
related
issues
to
that
Epic.
B
Those
issues
need
to
be
from
projects
in
that
same
hierarchy,
so
that
project
needs
to
actually
live
underneath,
like
a
single
top
level
group.
Fortunately,
we
do
have
a
capability
or
process
to
transfer
projects
from
one
group
to
another.
I
can
share
some
documentation
to
help
you
consolidate,
but
I
can
also
give
you
a
brief
demo
here
in
in
a
sandbox
environment
that
I
have
here.
So
if
I
wanted
to
move,
say
this
get
Ops
project
or
gitlab
coffee
shop
project.
That's
in
this
administrator
namespace.
B
On
my
self-managed
instance,
I
can
just
go
to
settings,
search
for
transfer
scroll
down
here
and
there's
a
transfer
project
section
here.
You
can
select
a
new
namespace,
which
is
essentially
a
top
level
group
that
we
can
move
it
to.
We
could
select
this
top
level
group
and
hit
transfer
project
and
it'll.
Ask
for
our
confirmation-
and
it's
just
as
simple
as
doing
that.
B
But
one
thing
to
keep
in
mind
is
that
this
is
something
that
you
want
to
be
really
careful
with,
because
the
repository
passable
change
and
a
redirect
will
be
in
place,
but
it'll
only
be
in
place
temporarily.
So
you
know
if
you've
got
active
development
going
on.
You
want
to
make
sure
that
you've
notified
your
users
to
update
the
repository
path
and
you've
got
robust,
CI,
CD
pipelines.
You
want
to
make
sure
that
you've
updated
any
references
to
the
old
path
to
the
New
Path.
A
B
Another
good
question:
so
I
get
this
often
when
I'm
meeting
with
customers
who
want
to
kind
of
standardize
on
how
their
epics
are
being
created.
Unfortunately,
no
we
don't
have
the
ability
to
create
a
template
for
an
epic
description.
We
do
have
an
open
issue
tracking
those
feature
request,
but
as
a
workaround,
you
can
create
an
issue
template
that
you
can
utilize
for
creating
new
issues,
but
maybe
call
it
an
epic
template
for
your
issues.
So
that
way,
when
you
create
a
new
issue
using
that
template,
you
can
then
promote
that
issue
to
an
epic.
A
B
Another
good
question
so
tackle
the
first
part
of
the
question
first,
so
the
minimum
role
that
you
want
to
provide
your
users
with
read-only
access
to
your
private
projects.
Repository
is
the
reporter
role,
so
I
can
share
with
you
actually
here
I
can
bring
up
the
permissions
Matrix
page,
so
in
our
gitlab
documentation
you
can
do
a
search
for
you
know
certain
keywords
to
kind
of
help.
B
You
drill
down
on
the
specific
actions
here
so
everything's
kind
of
in
a
table
format
and
if
you're,
looking
on
the
action
to
view
project
code,
you
can
do
a
search
on
the
page
here
and
you
can
find
exactly
what
roles
can
be
assigned
to
a
user.
So
that
way
they
can
view
project
code,
there's
a
one
here
next
to
the
guest
role,
because
the
guest
rule,
if
you
assign
that
to
a
user,
the
guest
role
is
only
available
to
our
ultimate
tier
customers.
B
A
B
Assigned
to
your
groups
and
projects
so
just
operating
with
the
concept
of
lease
privilege,
you
know
assigning
your
your.
Your
team
members
would
say
like
the
reporter
role
and
then
elevating
their
access
if
they
need
to
actually
create
new
branches,
so
giving
them
the
developer
role
and
then,
if
they
need
to
do
any
additional
work,
that's
elevated
from.
A
Awesome,
thank
you
and
thank
you
everyone
for
joining
us
today.
We
appreciate
you
taking
some
time
out
of
your
busy
days
to
to
learn
gitlab
with
us
and
with
that
we'll
we'll
wrap
up
today
and
like
we
mentioned
at
the
beginning,
you
can
expect
to
see
the
recording
here
the
next
day
or
so
thanks.
Everybody.