►
From YouTube: Intro to GitLab Webinar
Description
Are you new to GitLab? Join this webinar, where we will review 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,
I
think
we
can
go
ahead
and
get
started.
We
have
a
a
good
number
number
of
people
in
the
webinar
here.
So
thank
you
for
joining
us
today.
We're
super
excited
to
be
going
through
an
introduction
to
git
lab
with
all
of
you.
I
appreciate
you
taking
some
time
out
of
your
day
to
spend
with
us
we'll
we'll
just
go
through
a
a
few
housekeeping
items
to
get
started.
A
A
I'm
on
the
technical
account
management
team
as
well
here
at
get
lab
and
I'll
be
your
host
today
but,
as
I
said,
just
a
couple
of
housekeeping
items.
First
off,
if
you
have
any
questions
that
come
in
throughout,
please
go
ahead
and
put
those
in
the
q
a
portion
of
zoom.
We
will
have
time
to
to
get
those
answered
towards
the
end
and
we
may
chat
answers
back
to
you
as
well,
so
looking
forward
to
to
providing
that
live
q
a
portion
of
this
session.
A
B
Great
thanks
taylor
and
thanks
again
for
everyone
taking
time
on
your
busy
days
to
join
us.
We
hope
you
get
some
useful
tips
and
tricks
and
and
getting
started,
helping
you
to
get
started
with
gitlab
today,
all
right.
So,
let's
dive
right
in
so,
first
and
foremost,
what
what
is
git
lab.
You
know
most
of
you
if
you're
coming
to
this
session,
you
are
new
to
gitlab
and
so
we're
going
to
go
going
over
kind
of
some
of
the
basics.
B
But
gitlab
is
a
complete
tool
for
the
entire
dev
setups
lifecycle.
We
started
as
a
git
repository
manager
and
and
then
we
quickly
grew.
We
added
ci
cd.
We
added
issue
tracking,
we
added
a
number
of
other
features
and
we
will
touch
on
some
of
those
today
and
some
of
the
other
ones
we
will
have
upcoming
sessions
and
we'll
have
a
link
at
the
end
for
the
upcoming
sessions
that
are
on
our
website.
B
So
if
you
want
to
register
for
those
we'll
be
going
through
some
of
these
in
more
detail,
because
today
is
fairly
high
level,
but
a
lot
of
good
information,
also,
we
are
an
open
source
platform.
So
our
our
code
is
open
source
and
all
of
our
issues.
Our
roadmap
is
all
open
to
the
public.
You
can
go
to
our
website
and
find
information
on
that,
and
you
can
even
comment
on
features
you'd
like
to
see
and
help
us
to
improve
the
direction
that
we're
going
with
gitlab,
and
we
welcome
that.
B
So
so
that's
a
little
bit
about
what
is
git
lab
now.
What
git
lab
kind
of
empowers
you
to
do
is
to
kind
of
migrate
from
older
ways
of
doing
software,
development
like
sequential
devops
or
maybe
even
waterfall
or
other
methods
like
that
into
concurrent
dev,
sec,
ops
and
we've
added
the
second
there
as
security.
So
it's
it's
development,
security
and
operations
all
working
together,
but
with
concurrent
devsecops,
which
you
can
do
within
gitlab,
because
we
cover
all
10
stages,
as
defined
by
gartner
of
the
software
development
life
cycle.
B
More
on
that
in
a
moment-
and
so
you
know
because
we
cover
all
of
those
in
a
single
user
interface,
a
single
application.
It
allows
your
team
to
work
together
with
seamless
collaboration,
full
accountability,
embedded
security
scanning,
where
you
can
know
any
issues
that
arise.
You
can
know
about
them
very
quickly
right
software
development
is
not
perfect.
B
There
are
going
to
be
mistakes
made,
but
you
need
to
know
about
them
early
and
and
often,
and
so,
if
whether
it's
a
security,
vulnerability,
you've
introduced
by
accident
or
a
bug
or
an
integration
issue
that
you've
introduced
gitlab
helps
you
to
learn
about
that
very
quickly
and
make
the
change
while
the
developer
is
still
working
on
it
rather
than
weeks
or
sometimes
months
down
the
road.
We
also
help
to
avoid,
if
you
have
problems
where
you
have,
teams
that
are
working
in
silos
and
you
have
handoff,
friction,
friction
or
finger.
B
Pointing
and
I've
worked
for
organizations
like
this
in
my
past
in
my
career,
and
it
is
not
fun
right.
I've
worked
for
an
organization
where
it
was
more
important
to
blame
the
failure
of
the
project
on
some
other
team
than
it
was
to
succeed
in
the
project,
and
that's
not
a
good
way
to
you,
know,
to
work
and
to
think
and
and
gitlab
really
empowers
you
to
to
work
together.
B
So,
as
I
mentioned,
the
the
concurrent
devstock
ops
life
cycle,
what
does
this
look
like?
So
this
is
one
view
and
this
kind
of
represents
the
loop
of
of
devops,
where
you
are
planning
your
work
and
gitlab
has
capabilities
to
help.
You
do
this
using
issues
and
epics
and
roadmaps
and
boards
and
labels
and
milestones
which
we'll
touch
on
a
little
bit
today.
But
you
can
do
all
of
your
planning
here
within
git
lab.
B
But
but
the
names
actually
came
from
gartner
when
they
did
their
analysis
on
devops,
so
we're
just
kind
of
adopting
them,
so
the
create
stage
is
really
where
you
are
writing
your
code,
and
this
is
where
kind
of
gitlab
started.
As
I
mentioned
earlier,
and
we
have
a
couple
different
ways:
you
can
do
that
you
can
use
git
on
your
local
machine
and
then
push
stuff
back
up
to
the
server
or
you
can
also
use
our
built-in
web
ide.
We
have
an
integrated
design
environment,
a
development
environment
built
into
gitlab.
B
I
actually
find
that
very,
very
useful
when
I
am
making
updates
to
our
documentation
or
updates
to
our
website.
I
don't
do
a
lot
of
coding.
I've
only
done
one
code
contribution
that
wasn't
documentation
in
my
time
at
gitlab,
but
I've
used
the
web
ide
just
because
it's
a
little
faster
and
easier.
When
you're
making
a
small
change
when
you're
making
a
big,
complex
change,
I
find
it
easier
to
work
locally
and
we
support
both
workflows
and
individuals
can
even
do
both
and
and
mix
and
match.
B
Our
verify
stage
is
where
our
ci
really
comes
into
play.
Our
continuous
integration,
where
it
can
automatically
build
and
test
your
code,
including
unit
tests,
integration
tests
and
even
you,
can
integrate
automated
ui
testing
tools
into
gitlab
into
the
ci
process
and
the
ci
itself
is
defined
in
a
code
in
a
in
a
configuration
file
that
lives
in
your
code,
repository
and
so
changes
to
it
are
managed
just
like
code,
and
you
know
if
you
accidentally
broke
the
ci
pipeline.
You
can
know
that
right
away
and
make
changes
right
away.
B
Package
and
release
are
part
of
kind
of
the
the
continuous
delivery
continuous
deployment
processes
within
git
lab
that
allow
you
to
more
rapidly
get
your
code
changes
in
a
working
state
into
your
customers
or
stakeholders
hands,
and
we
talk
about
these
more
in
the
cicd
webinar,
which
is
coming
up.
So
take
a
look
for
that.
B
Just
so,
you
can
see
those
ten
stages,
just
in
a
line
and
just
really
just
re-emphasizing.
The
fact
that,
with
git
lab,
you've
got
a
single
user
interface
single
place
where
you
can
have
conversations
and
discussions
on
the
the
topics
at
hand.
Everything's
in
a
single
data
store
with
a
single
permission,
model
and
governance,
security,
collaboration
and
analytics
are
all
built
in
and
so,
and
keep
in
mind
that
you
don't
have
to
switch
and
use
gitlab
for
all
of
these.
B
You
can
adopt
them
periodically
over
time
and-
and
you
can
actually
we
play
very
nicely
and
have
a
lot
of
open
source
integrations
with
a
lot
of
the
tools
that
are
in
the
industry
that
cover
some
of
these
stages.
So
if
you're
you're,
starting
with
using
some
other
tools
and
you're
using
gitlab
for
a
few
of
these,
you
can
start
that
way
and
then
check
out
what
gillette
has
to
offer
in
those
other
stages
and
slowly
adopt
those.
So
those
are
all
options
that
you
can
do
with
gitlab
all
right.
B
So
let's
talk
a
little
bit
about
the
gitlab
recommended
process.
Now
now
gitlab
is
very
flexible.
You
do
not
need
to
immediately
you
don't
you
don't
have
to
use
gitlab
this
way,
but
I'm
going
to
talk
a
little
bit
about
how
we
recommend
you
use
it,
and-
and
you
can
always
start
with
where
you
are
and
make
small
changes
to
approach
this.
If
you
like
the
benefits
of
what
we're
going
to
discuss
and
you'll,
see
this
slide.
B
If
you
attend
our
future
sessions,
you'll
see
this
slide
or
a
similar
one
in
almost
every
session,
because
I
like
to
focus
in
and
emphasize
some
of
the
different
areas
that
we'll
be
talking
about,
and
today
we'll
do
it
kind
of
in
general.
So
if
you
can
imagine
this
bottom
line
here
is
your
default
line
of
code.
B
B
B
You
can
do
code
reviews
all
of
this
seamlessly
within
the
merge
request
and
by
creating
it
early,
you
can
see
all
the
history
all
the
discussions
and
then
you
can
set
up
approvals
as
well
within
the
merge
request
process
that
your
team
can
use
to
to
make
sure
that
this
change
is
what
people
wanted.
What
is
not
causing
any
issues
is
not
causing
any
security,
degradations
that
are
not
acceptable
and
so
on,
and
then,
when
you
finally
merge
it
back
in,
you
can
have
confidence
that
change
is
going
to
be
successful.
B
Whenever
you
do
that
and
push
those
up
to
the
server,
your
ci
pipeline
will
automatically
run
that
will
automatically
build
and
test
your
code,
and
then
you
can
also
have
our
security
scans
run.
We
have
various
security
scans
that
are
available,
including
static
code
scanning,
license
compliance
dependency,
scanning
container
scanning
and
more.
B
You
can
also
deploy
out
to
a
temporary
review
app
if
you're,
using
docker
containers
or
kubernetes,
or
you
can
even
use
this
to
push
out
to
a
test
environment
and
the
review
app
allows
stakeholders,
customers
teammates
to
take
a
look
at
the
the
actual
running
application.
With
these
changes,
if
you
want
within
the
merge
request,
you
can
also
have
discussions
code,
reviews,
security
reviews
all
happening.
You
can
actually
reference
lines
of
code
or
and
create
kind
of
a
task
list
for
the
developer.
B
When
you're
doing
your
code,
review,
gitlab
is
100
remote
company
and
we
built
in
features
to
make
it
easier
for
us
to
do
these
types
of
processes
asynchronously,
because
it
wasn't
really
convenient
for
us
to
try
and
do
all
of
the
code
reviews.
You
know
synchronously
like
with
two
people
sitting
next
to
each
other
or
even
over
a
zoom
session,
so
we
built
in
pieces
to
help
teams
to
do
this,
asynchronously,
which
really
helps
today,
where
you
might
have
distributed
teams.
B
You
might
have
teams
working
folks
working
from
home
or
from
other
offices
that
you
need
to
collaborate
with
and
then
ultimately,
approvers
can
review
all
of
this
information.
Any
changes
that
come
out
of
this
will
reset
the
process
and
new
changes
will
rerun
the
pipeline
and
so
on.
Once
everybody's
happy
with
the
changes,
the
merge
requests
can
then
be
merged
by
someone
with
approve
with
mana
the
right
permissions,
and
that
can
then
kick
off
your
deployment.
B
B
You
may
have
heard
some
of
what
gitlab
calls
things
slightly
different,
so
I
wanted
to
create
this
kind
of
little
cheat
sheet
for
you,
so
that
you
will
understand
what
the
get
lab
objects
are
and
and
what
their
purpose
are.
We
we've
already
mentioned
a
few
of
them,
but
let
me
just
quickly
go
through
these.
So
fundamentally
in
in
gitlab,
a
project
is
where
your
code
lives.
It's
also
where
your
issues
and
merge
requests
live.
You
might
have
heard
this
as
a
as
a
repository
in
other
systems.
B
A
group
is
a
collection
of
projects.
You
can
have
groups
and
subgroups
and
sub
subgroups,
they're
kind
of
like
folders.
In
some
other
systems,
those
might
be
called
projects,
so
there
may
be
some
confusion,
but
I
wanted
to
make
sure
it's
clear
issues.
Is
our
generic
kind
of
place
to
discuss
the
changes
and
it
gives
you
a
place
to
do
planning
and
it
can
represent
a
story.
It
can
represent
a
feature
it
could
represent
a
bug.
It
can
even
just
represent
a
task
that
needs
to
be
done.
B
B
B
Epics
are
a
way
to
collect
related
issues
across
groups
and
projects
to
organize
them
by
theme,
and
so
what
this
allows
you
to
do
is
create
a
broader
piece
of
work.
So,
if
you
create
an
issue
that
redmi
represents
a
new
feature,
you
might
quickly
discover
that
that
feature
is
a
lot
bigger
than
you
thought.
You
need
to
break
it
down
into
other
issues.
B
Gitlab
allows
you
to
promote
that
issue
into
an
epic
and
then
start
creating
issues
underneath
the
epic,
and,
if
that
epic,
you
use,
discover
you
know
what
I
need
sub
epics
to
define
this
epic
and
break
it
down
even
further
and
then
break
those
down
into
issues.
You
can
do
that
within
gitlab
as
well.
B
B
Labels
apply
to
issues
and
epochs
and
merge
requests
in
our
way
to
tag
and
track
work.
We
have
the
ability
to
create
scoped
labels,
which
create
kind
of
a
name
value
pair,
so
you
can
have
only
one
of
each
type
or
you
can
create
regular
labels
that
are,
that
can
be
used
for
all
kinds
of
different
purposes
and
they're
completely
customizable
by
you
and
your
team,
and
you
can
create
them
at
the
group
level
or
project
level,
so
they're
available
to
everything
below
those
levels.
B
B
Really
the
it's
limitless.
What
you
can
do
with
boards
there's
a
lot
of
different
options,
and
I
think
we
have
one
a
couple
examples
coming
up
later
and
then
we
also
have
ways
to
group
issues
into
kind
of
time
blocks
using
milestones,
which
can
represent
program
increments
or
releases
or
even
sprints.
And
then
we
also
have
a
relatively
new
feature.
But
it's
been
around
for
a
while
now
and
it's
pretty
mature
called
the
iteration,
which
is
designed
to
kind
of
represent
a
smaller
time
period.
B
Maybe
a
sprint
or
something
like
that
and
in
a
single
issue
can
be
in
one
milestone
and
one
iteration.
So
it
allows
you
to
kind
of
have
it
in
a
release
and
a
sprint
as
an
example
and
then
finally,
we've
got
road
maps
which
allow
you
to
do
a
visual
representation
of
the
epics
or
sub
epics,
and
and
look
at
that
on
a
kind
of
gantt
chart
style
to
kind
of
visualize.
What's
coming.
B
B
Epics
do
live
in
the
groups
currently,
and
the
important
thing
to
understand
here
is
that
all
of
our
permissions
kind
of
flow
down.
So
if
I
add
someone
with
a
specific
permission
at
the
group
level
top
group
level,
they
will
automatically
have
that
permission
level
or
more
permissions
at
the
subgroup
and
project
level.
So
it's
important
when
you're
adding
folks,
you
might
want
to
add
them
with
the
lowest
permission
that
you
want
them
to
have
at
the
top
level,
and
then
you
can
always
so
say
so.
B
B
If
you
create
them
at
the
top
group
level,
they
will
be
available
to
all
of
the
subgroups
and
projects.
So
if
you
have
unique
labels,
you
can
create
them
at
the
lower
level
and
they
will
only
be
available
to
at
those
lower
levels.
So
everything
is
kind
of
top
down.
That's
important
to
understand
and
remember,
when
you're
getting
started,
and
also
when
you're
thinking
about
how
to
organize
your
your
gitlab
instance,
based
on
the
projects
that
you
currently
have.
B
So,
like
I
said
before,
you
might
create
an
issue
to
discuss,
maybe
start
applying
some
different
labels,
maybe
apply
a
discussion
label
so
that
people
know
it's
in
that
stage
and
you
start
we
we
within
the
issues
and
the
merge
requests
and
ethics.
We
have
comments
and
threaded
comments
that
you
can
use
to
discuss
it.
B
And
then,
ultimately,
maybe
you
mark
it
as
ready
for
documentation
or
marketing
to
get
involved,
because
there's
tasks
that
they're
going
to
need
to
do
and
and
then
remove
those
labels
when
those
are
complete
and
then
ultimately,
when
it's
ready
to
go
into
production,
the
release
team
would
merge
the
the
merger
crust
and
deploy
the
feature
to
production
and
then
closes
close
the
issue.
So
just
to
kind
of
give
you
a
little
bit
more
detailed
example
all
right.
So
enough
talk
about
the
concepts.
B
All
right
so
with
so.
This
is
what
a
group
when
you
first
go
to
a
group
page
in
get
lab,
and
this
is
a
demo
group
I
created
just
called
the
kevin
chassis
group
very
original,
a
couple
things
you'll
notice.
On
the
left
hand,
side
in
gitlab,
you
have
based
on
where
you
are
so
right
now
we're
looking
at
a
group.
B
B
I
can
view
the
issues.
Well,
that's
that's
weird
kevin
just
said
that
issues
live
in
projects,
not
groups.
Well,
what
this
is
doing
is
giving
you
a
view
of
all
of
the
issues
that
are
in
all
of
the
projects
underneath
this
group
same
thing
with
the
merge
requests
and
when
you
look
at
like
our
security
dashboards,
you
can
look
at
the
security
results
of
all
of
the
projects.
Kind
of
pulled
together
that
are
in
this
group.
B
So
if
I
look
at
these
views
from
this
higher
group
level
and
then
if
I
go
into
one
of
these
lower
groups
that
you
can
see
here
listed
in
the
main
body
view
where
it
shows
me
the
hierarchy
of
all
the
subgroups
and
ultimately
I
can
see
the
projects
with
the
group
icons
being
the
folders
and
the
project
icons
being
kind
of
like
ribbon.
Then,
when
I'm
doing
this
view
from
this
level,
I
will
see
more
issues
than
if
I
do
it
from
a
lower
level,
and
that
can
be
really
really
useful.
B
Same
thing
is
true
for
board
views
and
so
on.
So
simply
by
navigating
to
a
higher
or
lower
level
within
the
hierarchy
of
the
groups
and
projects,
you
can
get
different
views,
which
may
be
very,
very
helpful
to
you
when
you're
organizing
things,
especially
if
you
have
like,
if
you're
a
manager
looking
at
resources
across
multiple
projects,
you
might
do
it
from
a
higher
level.
If
you're
a
team
lean
on
an
individual
project,
you
may
want
to
just
filter
out
all
the
noise
and
just
look
at
these
views.
B
At
the
project
level,
which
we
will
show
you
in
a
minute,
you
can
also
see
some
information
about
the
group.
You
can
create
new
subgroups
and
new
projects
from
here.
We
will
come
back
to
that
later
and
then,
like
I
said
before,
you
can
see
the
hierarchy
of
all
the
subgroups
and
projects
and
you
can
kind
of
expand
these
and
then,
when
you
click
on
one,
you
will
actually
drill
down
into
that.
You
can
also
get
a
quick
preview
of
how
many
subgroups,
how
many
projects
are
directly
in
that
group
and
so
on.
B
So
there's
a
lot
of
information.
You
can
kind
of
glean
just
from
this
initial
group
level,
page
all
right.
So
let's
go
ahead.
In
this
case
I
clicked
on
the
epics
menu
and
what
this
did
is
it
expanded
the
epics
menu
into
a
sub
menu.
So
each
of
these
will
have
sub
menus
when
you
mouse
over
them,
you'll
see
them,
and
what
this
does
is
immediately.
B
If
I
just
click
on
the
epics,
it'll
immediately
bring
me
into
the
list
view,
which
is
the
top
sub
menu
item,
and
within
the
list
view
it
will
show
me
a
list
of
all
of
the
epics
that
belong
again,
I'm
still
in
the
kevin
chassis
group.
So
you
can
see
this
didn't
change.
All
I
did
is
change
my
main
view
from
that
group
overview
view
to
this
epic
list
view
and
then
within
the
epic
list.
I
can
scroll
through
these,
but
I
also
can
search
for
filter
and
I'll
show
some
examples
of
that.
Coming
up.
B
You
can
filter
by
various
fields
and
I'll
show
some
examples
of
that.
Coming
up.
You
can
also
view
all
of
the
open
issues.
Epic,
sorry
closed
or
all
you
can
do
a
bulk
change
to
the
epics
or
create
a
new
epic,
and
you
can
change
the
sort
by
and
the
sort
direction
and
then,
when
you're
viewing
these,
you
get
a
information
about
them.
You
can
see
the
issue
epic
number,
how
long
ago
was
created,
what
dates
it
spans
when
it
was
last
updated?
B
C
B
That
will
show
you
some
tips
and
tricks
with
markdown,
but
basically
mark
gen
is
a
fairly
used
industry
standard,
but
it
allows
you
to
format
format
text
simply
in
a
plain
text
way
and
store
it
as
plain
text,
and
so
it's
it's
very
useful
and
there's
a
lot
of.
We
support
all
the
base,
markdown
capabilities
and
we
actually
have
extended
it
to
include
some
other
helpful
things
that
are
specific
to
get
that.
So
you
can
see
that
here
with
the
description
we've
got.
B
B
On
the
right
hand,
side
is
kind
of
the
metadata
associated
with
this
epic.
So,
on
the
right
hand,
side
you
can
see
all
of
the
kind
of
metadata
associated
with
it.
We'll
also
see
this
view
coming
up
for
issues
and
see
how
different
it
is,
as
well
as
for
merge
requests.
So
with
the
epic.
You
have
a
start
date
and
a
due
date.
B
These
can
be
either
fixed
where
you
set
them
manually
or
they
can
be
inherited,
meaning
that
it
comes
from
the
issues
within
it
and
what
milestones
they
have
been
associated
with.
So,
if
you
create
a
bunch
of
issues
within
an
epic
and
assign
them
to
milestones,
the
epic
can
automatically
pick
up
its
duration
off
of
those
or
you
can
set
it
as
a
fixed
start
and
end
date.
B
B
If
you,
if
there
were,
you
would
see
those,
and
I
think
I
have
an
example
of
that
coming
up
and
you
can
also
see
the
people
who
are
participating,
so
the
participants
are
people
who
created
the
epic
were
at
mentioned
in
the
epic
added
comments
to
the
epic,
those
all
become
participants
and
they
will
get
notifications
on
further
updates
or
you
can
subscribe
to
this
epic
by
turning
on
notifications.
Similarly,
you
can
do
this
for
issues
and
merge
requests
as
well.
B
If
we
scroll
down
on
the
epic,
you
can
then
see
the
sub
epics,
and
these,
like
the
group
view,
are
all
hierarchical
and
expandable
and
dynamic.
You
can
then
expand
these
and
then
view
so
epics
will
show
up
with
like
the
stack
of
papers,
whereas
the
issues
show
up
as
this
kind
of
individual
sheet
of
paper,
and
so
you
can
expand
these
to
see
the
sub
epics
and
the
issues
within
them.
B
B
We
also
have
the
ability,
within
the
issues,
to
mark
them
as
on
track
or
at
risk,
and
you
can
see
those
here
and
it
rolls
up
those
if
they're
set
for
an
issue
up
to
the
epic
levels.
You
can
quickly
see
how
many
issues
are
on
track
are
at
risk
here
and
then,
on
the
right
hand,
side.
Everything
else
is
pretty
much
this
the
same.
B
Okay,
so
let's
move
on
to
issues,
if
I
click
on
the
issues
within
this
kevin
chassis
group,
it
will
again
bring
me
to
an
issue
list.
Where
again,
I
can
do
a
search
again,
I
can
sort
I
can
create
new
project.
I
can
create
a
new
issue.
I
can
bulk
edit
issues,
I
can
view
open,
closed
and
all
issues,
and
so
on
and
again
I
get
a
view.
B
How
many
merge
requests,
how
many
comments
and
all
of
the
labels
as
well.
So
there's
a
lot
of
information.
You
can
kind
of
glean
at
a
glance
and
you
can
see
there's
a
lot
of
variety
with
the
labels.
You
can
use
them
for
workflow
for
priority
for
something
that
needs
attention
for
sentences
assigned
to
us.
You
know
for
something
that
is
a
capability
versus
a
bug
or
whatever
you
can
use
them
for
bug
or
feature,
and
so
on.
B
So
there's
a
lot
of
variety
and
these
tylenol
kind
of
looking
like
items
are
the
scope
labels.
So
here
you
can
see.
This
is
a
workflow
in
the
testing
stage
of
my
workflow,
this
one's
in
the
doing
stage
of
my
workflow
so
and
these
are
completely
customizable,
so
you
can
create
them
and
make
them
whatever
you
want.
B
B
B
I
can
clear
it
create
new
ones
and
so
on
and
by
the
way,
when
you
update
these
views,
it
does
update
the
url,
and
so,
if
you
share
the
url
of
bookmark
it
whoever
clicks
on
it
will
get
this
exact
same
view
with
all
the
filters
and
sorts
and
everything
already
built
in,
because
the
url
is
continuously
updating
in
your
browser.
As
you
make
changes.
B
B
B
So
when
you
create
a
new
one
it
you
can
have
a
list
of
templates
to
choose
from,
and
those
templates
are
simply
marked
down
files
that
are
stored
in
a
specific
location
and
you
can
edit
those
and
maintain
those
so
that
you
can
improve
the
templates
over
time
and
we
we
do
that
and
use
them
quite
heavily
within
gitlab.
On
the
right
hand,
side
you
have
all
of
the
metadata
associated.
B
You
can
see,
there's
a
little
bit
more
with
issues
than
epics
epics
don't
have
assignees,
but
in
issues
you
can
have
not
only
assignees,
but
you
have
multiple
assignees
you
can
see
which
single
epic
it
belongs
to
an
issue
can
belong
to
one
epic.
Only
you
can
see
the
milestone
belongs
to
this
is
actually
an
older
screenshot,
but
there's
also
an
iteration
that
it
can
belong
to
if
you're
doing
time,
tracking,
you
can
see
what
the
estimate
and
how
much
time
has
been
spent
against
it.
B
You
can
see
the
issue
weight
issue
weight
is
a
way
to
determine
the
difficulty
of
us
of
an
issue
and
use
it
in
planning
and
it
shows
up
in
the
boards
and
the
burn
down
and
burn
up
charts,
and
it's
simply
an
a
positive.
It
just
needs
to
be
a
positive
whole
number,
so
an
integer,
but
it
can
be
anything
you
want.
So
if
you
have
a
system
you're
using
today,
as
long
as
you
can
relate
that
into
positive
whole
numbers,
you
can
continue
to
use
those.
B
So
if
you're,
using
like
fibonacci
sequence,
that
works
quite
well,
if
you're
doing
something
like
t-shirt
sizes,
you
might
need
to
convert
those
into
numbers
again
because
the
we
we
actually
add
those
numbers
up
to
show
them
to
you
on
boards
and
other
charts.
So
it's
it's
useful
to
have
that
as
a
number
that
can
be
added.
If
you
choose
not
to
use
weight
well
effectively,
everything
has
a
weight
of
one
then
right,
because
everything
is
just
counted
as
a
single
issue
and
some
teams,
you
may
do
it
that
way
as
well.
B
So
and
then,
finally,
you
can
this
confidentiality
setting
if,
if
you're
in
a
private
project,
there's
really
no
no
need
to
use
the
confidentiality,
because
only
members
of
your
project
can
see
the
issues,
but
you
can,
when
you
create
your
projects,
you
can
create
them
so
that
anybody
who
can
get
to
the
url
can
see
it.
So
that's
a
public
project
and
then
you
can
also
create
instance,
wide
projects
where
anybody
who
has
a
log
into
your
git
lab,
even
if
they're,
not
member
of
the
project,
can
see
it.
B
B
I
will
upvote
the
items
I'm
following
and
then
I
can
quickly
see
how
many
are
released
by
creating
a
filter.
That
says
show
me
everything.
That's
in
the
next
release
that
I
uploaded
and
and
then
I
get
a
list
of
those
which
is
really
neat,
but
you
can
do
that
for
other
emojis,
too
and
so
on,
and
then
you
can
see
all
of
the
discussions.
B
B
Oh
and
here's
the
example
of
a
group
discussion,
so
here
you
have
threaded
discussions.
So
this
is
the
main
comment
and
then
you
can
collapse
this,
but
these
are
all
the
sub
comments,
which
is
nice,
because
some
systems
that
you
work
in
doesn't
allow
you
to
do
this.
It
just
gives
you
a
list
and
then
it's
hard
to
tell
who
is
replying
to
whom,
whereas
here
it's
very
easy
and
then
here's
an
example
of
those
related
issues
that
I
mentioned
earlier.
B
All
right
just
a
couple
more
to
go
through
and
then
we'll
open
up
the
questions
as
a
reminder,
if
you
thought
of
questions,
feel
free
to
put
them
in
the
q
a
and
if
it's
something
that's
quick
and
easy,
we
actually
have
a
couple
members
from
the
tan
team
on
today.
They
can
help
answer
questions
or
I
will
take
them,
live
at
the
end,
so
feel
free
to
put
them
in
the
q,
a
as
you
think
of
them
as
we're
getting
closer
to
the
q,
a
portion.
B
So
all
right,
let's
take
a
look
at
boards,
so
under
the
issue
sub
menu
is
the
board
view
and
again
I'm
I'm
here
at
this
kevin
chassis
group
level,
and
I
am
looking
at
the
boards.
This
is
showing
me
all
of
the
issues
as
a
sync
at
each
rectangle.
Each
card
represents
an
issue
and
it
gives
me
a
little
bit
more
detail
at
a
glance.
B
I
can
drag
and
drop
these
across
the
columns
and
when
you
create
the
board,
you
can
actually
switch
between
boards
up
here
and
you
can
create
as
many
boards
as
you
want
and
name
them.
What
you
want
and
define
them,
how
you
want,
and
so
each
board
can
have
a
different
set
of
columns,
different
set
of
built-in
filters.
B
I'm
not
going
to
go
into
a
lot
of
the
detail
today,
but
there's
a
lot
of
neat
and
powerful
things
you
can
do,
but
let
me
point
out
a
few
things
so
on
the
left.
You
always
have
the
open
items,
which
means
that
these
are
the
issues
that
don't
match
any
of
the
columns
in
this
board
and
then
over
to
the
right.
You
see
this
little
scroll
bar
over.
All
the
way
to
the
right
is
the
closed
one.
So
every
every
issue
that's
closed.
That
matches
the
filter
criteria.
B
B
Then,
when
you're
looking
at
the
issues,
you
can
see
a
lot
of
information.
The
headline
the
labels,
the
due
date,
the
weight
which
project
it's
in
who
it's
assigned
to
and
when
I
drag
an
item
from
here
to
here,
it'll
automatically
apply
the
label
that
is
at
the
top
of
the
board.
But
you
don't
just
have
to
define
your
columns
by
labels.
You
can
have
columns
defined
by
people,
so
you
can
use
it
for
resource
planning,
drag
it
and
assign
it.
B
You
can
have
it
for
milestones
and
iterations,
so
you
can
assign
things
to
sprints
or
releases
or
program
increments
or
whatever
you're
using
those
for
or
you
can
do
it
for
labels
and
then
with
the
labels.
Like
this
example
is
a
triage
board,
so
I
have
all
my
priority
labels
across
the
top
in
the
order
that
I
would
work
them.
B
I
might
have
one
that
has
all
my
workflow
steps
in
order
so
that
I
can
quickly
see
where
things
are
in
the
workflow
and
move
things
as
needed,
and
I
could
filter
that
down
to
a
given
release
or
a
given
sprint
or
a
given
resource
or
even
just
create
one.
That
is
all
the
items
assigned
to
me.
So
I
can
quickly
see
all
the
stuff
I
need
to
work
on,
so
the
it's
really
limitless.
B
You
can
actually
create
or
add
issues
directly
here
or
you
can
mark
settings
for
this
column.
You
can
set
work
and
progress
limits,
so
the
column
will
turn
red.
If
you
exceed
it,
you
can
also
collapse
these
columns.
So
it's
easier
to
see
if
you're,
only
working
in
a
specific
area,
because
these
boards
sums
with
a
scroll
bar.
B
If
you
don't
have
a
wide
enough
monitor
it
will
you
know
it's
helpful
to
collapse?
Those
and
those
are
the
major
features
I
wanted
to
point
out
on
the
boards
all
right.
Let's
talk
about
the
merge
request,
so
we
mentioned
it
earlier.
So
this
is
what
one
actually
looks
like.
So
this
is
on.
The
left
is
the
top
portion
of
the
boards
request.
You
have
the
headline.
B
You
can
see
it's
associated
with
this
issue
and
it's
actually
going
to
close
the
issue
automatically.
If
you
use
the
closes
keyword
when
it
gets
merged,
if
it's
merged
successfully,
you
can
see
the
branch
that
it's
associated
with
and
where
the
target
branch
is.
So
if,
if,
if
you're
doing
a
branch
off
of
a
feature
branch,
you
might
you
know
you
might
not
be
into
your
main
branch,
it
might
be
into
a
different
branch.
B
You
also
have
the
ability
to
open
this
branch
in
the
web
ide
or
when
you
hit
the
checkout
brunch
it'll,
give
you
some
commands
that
you
can
copy
and
run
on
your
local
machine
to
clone
this
project's
repository
locally
and
work
with
it
locally
and
switch
to
the
specific
branch.
You
can
also
see
your
pipeline
results,
so
the
last
pipeline
to
run
which
commit
triggered
it
on
which
branch
and
you
actually
can
see
a
quick
overview
of
the
different
stages
in
your
pipeline.
B
We
will
cover
that
in
the
cicd
webinar,
which
is
coming
up
soon.
You
can
see
if
it
was
deployed
out
to
a
review,
app
or
a
testing
environment
when
it
was,
and
even
click
this
to
open
that.
If
there's
approvals
required,
you
can,
if
you're
authorized
to
give
approvals,
you
can
approve
or
revoke
your
approval,
and
you
can
also
view
the
eligible
reprovers
there's
a
whole
process
where
you
can
create
different
rules
and
sets
of
approvers.
B
And
then,
when
you
start
a
code
review,
you
can
add
additional
items
to
the
review
and
then,
when
the
developer
comes
back
and
looks
at
it,
they'll
see
that
they
have
unresolved
threads
to
resolve.
They
can
do
that
by
making
additional
code
changes
or
by
replying
and
explaining.
Why,
and
so
you
can
do
the
code
review
asynchronously
like
that.
B
We
empower
you
to
do
automated,
builds
and
tests
and
encourage
collaboration
across
all
of
your
teams
to
make
it
easy
to
view
the
results
and
see
what's
going
on,
and
then
this
is
an
example
graph
here
that
shows
you
the
difference.
You
can
organize
your
pipeline
into
stages
which
happen
sequentially
and
you
can
have
multiple
jobs
in
a
single
stage
that
happen
in
parallel.
You
can
see
the
status
you
can
rerun
them.
B
B
And
then,
just
a
couple
more
and
we'll
go
to
questions
apologize,
I'm
running
a
tiny
bit
long,
but
we
will
have
some
time
for
questions
and
I
see
there
is
one
but
we'll
get
to
that.
In
a
moment.
This
is
a
view
of
the
labels.
I
just
wanted
to
show
you
this
what
this
looks
like,
so
I
have
it
filtered
for
just
the
priority
labels,
and
you
can
see
how
I
created
a
series
of
priority
labels.
B
You
can
edit
these
you
can
see
which
group
they're
coming
from.
If
I
created
them
at
a
higher
group
level,
you
can
also
click
on
these
to
view
all
of
the
issues.
With
that
label
merge
requests,
you
can
even
subscribe
to
a
label.
So
if
someone
applies,
it
you'll
get
an
email.
So
if
you're
a
member
of
the
marketing
team-
and
they
apply
that
marketing
label
we
talked
about
earlier
as
an
example,
you
get
a
notification
same
thing
with
documentation
or
security,
or
you
know
it's
really
endless
what
you
can
do.
B
Then,
with
the
milestones,
this
is
the
milestone
view.
If
you're
looking
at
the
list
of
milestones,
you
can
see
the
dates
the
milestone
is
set,
for.
These
are
always
fixed
dates.
How
many
issues
and
merge
requests
and
how
far
along
you
are,
and
if
you
click
on
one
of
the
milestones
to
drill
into
it,
you'll
get
a
burn
down
and
burn
up
chart
which
I
don't
have
a
screenshot
of
today
and
then
some
quick
navigation
tips.
B
So
we
talked
about
the
left
menu,
but
I
also
wanted
to
mention
there's
this
breadcrumbs
that
are
at
the
top,
and
I
also
talked
earlier
about
the
url
that
changes
depending
on
where
you
are
so
you
can
copy
and
paste
the
url.
So
these
are
just
some
quick
navigation
tips
and
then
that
dot
dot.
If
you
click
it,
it
will
give
you
the
full
list
of
all
of
the
different
hierarchy.
So
I
can
click
on
an
individual
one
of
these.
B
B
B
A
Yeah
we'll
go
through
this
super
quick
and,
as
I
do,
please
feel
free
to
put
your
questions
in
the
q.
A
just
wanted
to
go
through
your
ongoing
support
and
upcoming
webinars
that
we
have
this
month.
First
off
for
support
issues
that
come
up.
You
can
see
there.
We
have
a
portal,
hopefully
everyone's
had
a
chance
to
take
advantage
of
that.
A
If
you
haven't
yet
please
go
ahead
and
submit
any
requests
that
that
you
have
at
that
at
that
support
portal
there
we
have
a
monthly
newsletter
as
well,
keep
an
eye
out
for
that.
We
have
highlights
from
our
monthly
release
and
we'll
continue
to
let
you
know
about
upcoming
sessions
that
we
have
and
then,
in
terms
of
webinars,
that
we
have
for
the
rest
of
the
month.
A
A
B
Thanks
taylor
appreciate
that
all
right,
so
q,
a
let's
see
we
have
one
question
right
now,
so
I'll
read
it
out
loud
for
everybody.
We
would
like
to
enable
our
developers
to
create
their
own
projects,
but
we'd
like
the
new
projects
to
inherit
all
of
the
settings
from
the
parent
group
as
designated
by
the
group's
owner,
such
as
the
default
branch,
push
rules,
integrations,
etc.
B
Is
that
default
behavior
for
all
new
descendant
projects
under
a
given
group
or
something
that
needs
to
be
templatized
automated
another
way?
So,
yes,
excellent
question,
there
are
some
things
that
you
can
inherit
from
the
group
and
we
are
working
to
make
that
more
robust
and
I
believe
chris
is
going
to
put
a
link
in
the
answer
to
that
question
that
has
a
link
to
our
policy
management,
documentation,
page
and
compliance
features
that
talk
a
little
bit
about
where
we
are
with
some
of
those
settings.
But
I'll
be
honest
with
you.
B
We
are
not
quite,
I
totally
get
what
you're
asking
for
and
we're
not
quite
where
you
would
want
to
be
where
you
can
basically
say:
every
new
project
is
going
to
have
all
of
these
different
things
set.
So
there's
a
couple
different
techniques.
You
can
use
to
mitigate
that
as
we
expand
in
our
roadmap.
Those
capabilities
for
you
one
one
is:
you-
can
use
our
api
to
to
check
the
projects
and
then
make
the
settings
changes.
B
I
have
a
couple
teams
with
some
of
the
customers
that
I
work
with
on
a
regular
basis
that
are
doing
it
that
way,
and
then
I
don't
know
chris,
if
you
had
anything
you
wanted
to
add
to
that
live,
but
that
that
that's
probably
the
best
answer.
I
can
give
you
for
that
right
now,
but
so
partially,
but
not
quite
100,
where
I'd
like
to
see
it,
because
I
do
get
what
you're
asking.
B
B
And
otherwise
I'll
give
you
another
minute,
but
while
you're
thinking
just
to
reiterate,
definitely
check
out
these
pages-
and
I
think
taylor,
like
you,
said
this
is
being
recorded.
So
I
think
we're
going
to
send
out
if
you
registered
for
the
webinar
you're
going
to
get
a
copy
of
the
slides,
I
believe
and
a
link
to
the
recording.
B
And
then
these
links
are
live
in
the
copy
on
the
pdf
of
the
slides
that
you're
going
to
get,
and
this
link
will
take
you
to
the
tam
webinar
page,
and
these
are
the
upcoming
ones
that
taylor
mentioned.
But
you
can
kind
of
go
back
and
look
for
further
ones
that
are
upcoming
in
the
future.
As
we
offer
more
more
webinars
to
help
help
you
all
get
the
most
out
of
your
investment
in
gitlab.
B
C
B
I'm
assuming
I'm
assuming
you
might
be
on
get
lab
dot,
com
or
or
maybe
you're
or
you're
on
a
self-managed.
I
I
guess
you
could
post
another
question
to
okay,
yes,
you're
on
gitlab.com
yeah,
so
yeah
that
can
be
a
challenge.
I
actually
find
that
challenging
myself.
Sometimes
when
I'm
trying
to
mention
another
gitlab
teammate
and
I
have
to
go
and
look
up
what
their
handle
is
trying
to
think
of
a
good
answer.
I
know
chris,
do
you
have
anything
that
you
would
want
to
suggest
for
this?
One.
C
Oh,
it
is
a
great
question.
I
don't
have
anything
off
the
top
of
my
head,
but
yeah.
I
would
certainly
the
autocomplete
can
kind
of
show
you
some
of
the
suggestions
there
and
then
you
know
I
would
recommend
opening
up
another
tab
to
just
verify
the
the
handle
that
it
is
somebody
that
you
intend
to
add.
But
I
you
know,
I
think
we
could
take
this
offline
and
then
follow
up
in
the
in
the
follow-up
email
to
share
some
other
right.
B
Yeah,
the
only
other
thing
I
can
think
of
real,
quick
and
I
know
we're
over,
but
is,
if
you
go
to
the
members
link
within
the
group
or
the
project,
I
think
you
can
search
by
email
within
the
the
the
project
or
the
group.
So
if
you
mouse
over
the
name
of
the
group,
there'll
be
a
thing
that
says
members.
B
Even
if
you
don't
have
permissions
to
add
people,
you
can
still
see
who
the
members
are,
and
I
think
you
can
filter
that
via
email
and
that
might,
if
you
know
their
email,
that
might
tell
you
what
their
username
is
because
yeah
there
are
a
lot
of
names
out
there.
So
great
question
thanks
so
much
and
looking
forward
to
seeing
you
in
a
future
session
and
enjoy
the
rest
of
your
day
and
week.