►
Description
This AMA was recorded during KubeCon North America 2020 and features a panel of GitLab Developer Evangelists answering questions from the wider GitLab community.
Panelists include:
- Abubakar Siddiq Ango
- Brendan O'Leary
- John Coghlan
- Michael Friedrich
You can find more videos featuring the GitLab Developer Evangelism team on this playlist: https://www.youtube.com/playlist?list=PL05JrBw4t0Kq-bYO9jCJaN45BBpzWSLAQ
A
I
I'll
do
an
introduction
of
myself
I'll
ask
the
other
folks
from
the
gitlab
developer,
evangelist
team
to
introduce
themselves
then
I'll
get
into
one
of
the
questions
that
was
pre-submitted
and
then,
if
folks,
who
are
on
the
call,
want
to
ask
questions,
we'd
love
for
you
to
verbalize
them,
if
not
we'll,
just
keep
going
with
the
pre-submitted
questions
until
other
folks
add
theirs.
You
know
verbally
or
in
the
chat.
So
first
of
all
thanks
everyone,
so
much
for
being
here
today,
we're
really
excited
to
be
hosting
this
ama.
A
This
is
the
first
time
we've
done
this,
so
it's
kind
of
an
experiment
for
us,
but
we
think
it's
a
really
great
way
for
us
to
just
connect
with
our
community
and
find
out.
You
know
what
people
are
thinking
about
and
hopefully
help
people
solve
some
problems
or
just
get
the
information
that
they
need
to
start
the
introductions.
I'm
john,
I
manage
the
developer
evangelism
team
at
git,
lab
I
also
or
previously,
and
I'm
still
running
our
gitlab
meetups
and
gitlab
heroes
program.
Although
we're
trying
to
to
fill
that
role.
A
B
Sure
sure,
thanks
john,
my
name
is
brandon
o'leary,
formerly
known
as
john
coghan
developer
evangelist
at
gitlab.
I've
been
at
get
lab
since
october
of
2017,
which
is
a
very
long
time.
In
startup
years,
I've
had
a
number
of
roles
at
gitlab.
I
helped
start
our
professional
services
organization
here.
I
then
also
ran
product
for
our
verify
stage
for
a
time
and
then
finally
got
converted
by
our
friend
priyanka
who's.
B
A
So
I
I
guess
you
know,
I
think,
let's
get
started
with
the
questions
and
then,
as
people
are
verbalizing
their
questions,
they
can
introduce
themselves.
I
think
that
would
be
a
great
way
to
do
it.
So
the
first
question
was
submitted
by
pascal
kramer,
who
I'm
not
seeing
on
this
call,
but
we'll
answer
the
question
anyway,
and-
and
hopefully
pascal
will
tune
in
to
the
recording
of
this
when
it
gets
posted
to
youtube.
A
So
pascal
asks:
how
can
us
set
up
an
empty
local
repo
which
will
actually
be
created
later
on
with
sub
modules
already
set
up?
How
can
I
think
he
meant?
How
can
I
set
up
an
empty
local
repo,
with
some
modules
already
set
up
and
michael
it
looked
like.
You
were
answering
that
question
in
the
doc,
so
you
want
to
verbalize
your
response.
D
Yeah
I
just
like
peeked
into
that
before
and
did
some
google
googling
and
I
kind
of
would
do
it-
would
solve
it
in
the
way
of
either
using
the
rest
api
actions
to
create
the
project
and
later
on
import
the
sub
modules
or
go
away
with
using
a
project
templates
for
groups
and
and
other
things.
So
this
would
be
one
thing
and
I
can
see
that
we
probably
should
also
be
sharing
the
urls
and
the
links
which
I
will
be
sharing
in
the
chat.
D
Oh
john
is
john,
is
already
copying
it.
So
I
haven't
said
anything
but
yeah.
That's
that
should
be
about
it
and
if
not,
I
would
recommend
joining
the
gitlab
forum,
which
can
be
reached
on
forum.gitlab.com
and
just
reach
out
and
ask
your
question:
maybe
there
to
find
out
more
how
our
community
members
solve
the
problem,
but
that's
basically
about
it.
How
I
would
solve
it.
A
E
Hi,
my
name
is
not
john.
It's
michelle.
I've
got
a
question
around.
The
cuban
needs
agent
you're
working
on.
If
you
have
more
information
about
that
general
availability
of
it,
what
is
the
idea
behind
it?
It's
going
to
function
as
an
operator
really
or
if
you
don't
know
anything
about
it,
that's
also
fine
or
if
you
need
to
google,
it.
B
Yeah,
no,
I
can
take
that
one.
I
was
writing
the
question
in
the
document.
So
I'll,
let
john
or
someone
else
write
the
answer
yeah.
So
the
kubernetes
agent
in
git
lab
is
going
to
be
yes
like
a
like
a
full
agent
that
runs
in
your
kubernetes
cluster
and
does
kind
of
pull
based,
get
ops
deployments,
and
so
it's
actually
based
on
the
open
source,
get
ops
engine
from
the
argo
project.
B
So,
if
you
look
at
that,
basically,
the
git
ops
engine
is
what
underlies
like
argo,
cd
or
argo
flux.
It
also
is
what
underlies
the
get
lab
kubernetes
engine
or
agent.
So
it's
basically
the
same
concept.
You
know
you
can
have
a
manifest
repository
that
the
agent's
watching
for
changes
and
then
it
applies
those
changes
whenever
there's
there's
an
update
to
that
yeah.
B
Good
question:
I
don't
think
I
it's
going
to
disappear.
I
think
the
idea
is
that
there
are
going
to
be
folks
that
want
to
do
kind
of
like
a
push-based
cd
to
kubernetes
and
that's
what
the
original
kind
of
kubernetes
integration,
if
you
will
in
get
lab,
where
there's
you
can
like,
create
a
cluster
or
put
the
details
of
your
cluster
in
that
allows
git
lab
to
push
changes
to
your
application
into
kubernetes.
B
B
The
plan
is
to
support
both
right
going
forward
because
there's
some
folks
that,
like
the
idea
of
a
push
based,
you
know
cd
deployment,
some
folks
that,
like
the
idea
of
a
pull
based
cd
deployment,
we
also
have
our
I
see
william
hiding
on
our
call
who's
our
get
ops
expert
on
our
product
marketing
team.
He
can
add
anything
that
I've
missed
there.
E
B
B
G
D
I
think
I
can
take
that
we
do
have,
I
think,
there's
a
left
cli.
We
also
have
a
two
other
different
projects
in
that
area.
We
had
ideas
of
integrating
or
like
migrating
the
lab
cli
into
our
workspace.
Currently,
so
there's
an
open
epic
around
that
which
I
need
to
google
now
and
the
thing
is
currently
there's
no
work
resources
assigned
to
it.
So
with
this
we've
been
discussing
it
on
the
developer
event,
listen
team
to
maybe
take
it
over,
and
we
are
also
in
contact
with
the
ecosystem
group.
I
think
so.
D
The
idea
is
there
and
I
think
the
demand
is
also
there,
but
currently
it's
kind
of
stuck
in
the
migration
of
the
lab
project
from
github
to
gitlab
into
our
organization
and
then
like
invite
everyone
to
work
on
it.
But
this
is
I've
just
pasted
the
pic
in
the
in
the
chat.
This
is
something
which
we
are
currently
discussing.
D
G
I
can
use
that
because
my
main
use
case
for
that
was
because
I
used
last
week,
I
used
for
the
first
time
the
new
github
cli
mostly,
and
they
have
a
function.
It's
called
ford
like
you
can
do
directly
at
did
for
and
it
will
pull
automatically
also
the
upstream.
So
you
have
everything
set
it
up
with
only
one
command.
This
really
quite
cool
way
of
working
as
an
open
source
developers
idea.
I
can
easily
only
forfeit
project
directly
and
have
directly
connected
upstream.
It
will
speed
up
a
little
bit
productivity.
G
I
only
used
as
a
lab.
I
used
only
one
time
this
like
a
year
ago,
or
something
right,
because
for
that
I
pro
I
need
to
program
also
a
small
tool
for
myself
to
doing
the
authentic
automatically
way
to
get
in
personal
access
token
from
the
cli,
and
for
that
I
looked
into
cli
to
its
mostly
their
written
in
ruby,
and
I
don't
know
ruby
at
all.
G
So
I
can
mostly
read
ruby,
but
I
can't
write
it
or
it
takes
too
long.
So
I
need
to
check
if
it's
in
the
other
programming
language
I
found
out
that
d-dap
was
currently
out
there
and
then
I
started
to
use
it.
But
I
think
for
that
time
they
didn't
that's.
My
didn't
have
my
problem,
but
it's
a
great
way
probably
to
contribute
that
to
the
gw2
to
see.
If
it
has
this
feature-
or
I
will
check
this
out.
B
H
So
I
would
have
a
small
one
same
direction,
but
more
the
project
management
part.
So
is
there
anything
blank
to
get
an
ios
or
android
app
for
managing
issues
and
stuff
like
this?
So
most
of
the
time
I'm
seeing
an
issue
update,
I
would
like
to
update
an
issue,
but
I'm
on
my
mobile
phone
and
would
be
nice
to
have
a
nice
integrated,
app
mainly
related
to
the
project
management.
F
A
Don't
personally,
I
don't
know
of
any
plans,
you
know
for
kind
of
an
ios
or
android
app
like
coming
becoming
available.
You
know
imminently.
I
know
it's
something
that
the
you
know
the
community
is
interested
in.
So
it's
it's
certainly
something
that
we
think
about,
but
I
don't
think
there's
any
kind
of
imminent
plans
for
that,
but
I
may
be
wrong.
Anyone
any
get
lovers
want
to
correct
me
on
that.
B
H
H
E
H
B
E
B
D
B
B
A
D
Yeah,
of
course
I
to
be
honest,
I
also
needed
to
research
a
little
bit
on
that.
It's
either
you
can
use
k-native
to
run
it
on
kubernetes
yourself
or
you
could
be
using
aws
lambda
and
integrate
it,
and
there
is
a
specific
documentation
around
that.
Full
disclosure-
I
haven't,
tried
it
myself,
but
this
could
be
something
to
have
a
look
into
it
and
should
also
support
the
way
of
either
running
your
local
kubernetes
cluster
in
your
own
dm
setter
environment
or
use
a
cloud
provider.
A
A
C
D
I
would
probably
add,
like
joining
our
meetups
and
doing
regular,
like
ci
cd
workshops
or
trying
things
out
together
and
have
a
peek
into
our
learning
platform,
which
also
showcases
how
features
work,
how
you
can
probably
solve
your
use
case,
and
maybe
let
yourself
inspire
you
by
kind
of
saying,
hey.
I
want
to
like
automatically
test
my
node.js
application.
D
How
does
it
work,
how
others
are
solving
it?
Probably
there's
already
a
blog
post
around
it
or
deft
you
resource
or
something
else
other
than
that.
If
you
happen
to
have
anything
which
will
say,
I
don't
know
how
to
to
go
any
further,
just
pull
us
in
on
on
either
on
social
media
or
even
better
on
on
the
forum
and
just
go
ahead,
asking
a
question
and
but
like
I
want
to
solve
like
this
problem,
or
maybe
I
have
this
project.
C
One
thing
I
would
like
to
add
also
is
most
times
we
tend
to
forget:
the
gitlab
youtube
channel
and
the
unfiltered
channel.
There's
a
treasure
trove
of
lot
of
videos
that
have
been
recorded
about
a
lot
of
things.
I
think,
almost
every
day,
new
videos
are
uploaded
to
the
unfiltered
channel.
You
can
get
very
good
videos
that
you
can
watch
on
about
different
aspects
of
gitlab.
There
also.
F
Just
that
I've
seen
the
links
in
chat
for
the
learn
section
of
the
website
and
just
something
I've
seen
that's
very
exciting
is
is
content
that
doesn't
even
come
out
of
get
lab,
but
there
are
a
lot
of
third
parties
that
will
do
how
to
learn,
get
lab
and
just
other
folks
in
the
community
that
are
not
the
key
left
team
members,
but
they're
excited
about
lab
and
they'll
put.
You
know
video
series
on
youtube.
The
one
thing
I
probably
would
recommend
is
to
try
to
find
the
latest
video
you
can.
F
So
there
might
be
a
really
amazing
series.
That's
really
well
done
terrific
communicator,
it's
probably
brendan,
but
he
probably
made
the
video
like
three
years
ago
and
gitlab
changes
so
quickly
that
you
can
get
really
confused.
In
fact,
I
literally
got
an
email
two
days
ago
from
somebody
who
watched
one
of
my
videos
on
using
epics
and
milestones,
and
they
emailed
me
and
they
said
hey.
I
love
your
videos
and
epic
milestones.
What
about
iterations,
because
iterations
were
shipped
like
right
after
I
did
the
video
so
like
immediately
my
video's
out
of
date.
F
So,
even
though,
there's
a
lot
of
really
good
content
out
there
with
like
that's
well
communicated,
I
probably
would
give
the
nod
towards
whatever
you
can
find.
That's
the
newest
or
the
freshest,
because
gitlab
changes
so
quickly
that
even
a
video
that's
a
few
months
old
might
already
be
pretty
meaningfully
out
of
date,
because
there's
some
new
feature
that
you
know
the
ui
has
changed,
or
it's
usurped
and
it's
exciting
part
about
gitlab.
We
keep
on
adding
new
things
very
very
quickly,
but
that's
the
tough
part
is,
is
finding
creating
how-to
content.
B
B
It's
gonna
sound,
really
silly,
but
like
the
fact
that
all
of
these
things
are
out
there
that
we
talked
about
right,
abubakar
talked
about
the
handbook.
Michael
talked
about
the
documentation
or
edward
talked
about
that
and
william
talked
about
the
videos
right
like
the
fact
that
all
that's
out
there
and
get
labs
open
with
all
that
means.
Google
is
actually
a
fantastic
like
index
of
how
to
learn.
Gitlab.
Like
any
time
I
I
just
like.
B
A
E
Yeah,
I
was
waiting
for
that
one
yeah
sure,
depending
on
where
the
users
come
from.
I
would
say,
first
of
all,
if
you
have
a
free
instance
or
something
installed,
if
a
basic
version
click
everywhere,
depending
on
the
permissions,
whether
this
person
is
an
admin
or
not.
Of
course,
if
you
have
the
possibility
to
be
added
as
an
admin
to
click
around
even
further,
do
that
personally,
I
think
you're
all
referring
to
other
documents
etc.
Do
with
google.
I
think
gitlab.
E
E
Basically,
some
things
might
not
be
completely
100
correct,
but
that's
when
you
get
into
the
installation
configuration
level,
you
might
have
some
additional
questions
about
what
certain
rate
commands
may
do
or
something
that's
really
the
I
would
say
the
deep
level
basic
permissions
are
always
very
important
to
read
about
what
the
dashboard
does
different
scopes.
One
can
have.
A
We
have
a
I'll
take
this
one.
We
have
a
shop.getlab.com
where
you
can
go
and
pick
out.
You
know
your
favorite
swag.
We
also
have
a
great
program
for
our
most
active
community
members,
people
that
contribute
either
code
or
write
blog
posts
to
tech
talks
about
git
lab
organized
meetups.
It's
called
the
gitlab
heroes
program.
A
I
run
that
program
and
I
think
the
t-shirts
are
awesome.
It's
a
it's
even
harder
to
get
than
just
your
standard,
gitlab
tanuki
shirt,
so
I'd
recommend
checking
that
out.
It's
called
get
lab
heroes
and
then
also
we
have
a
git
lab
community
day
coming
up
on
december
1st,
if
you're
part
of
the
gitlab
virtual
meetups
group
you'll
be
able
to
to
find
it
there,
if
not
search
for
gitlab
virtual
meetups
on
meetup.com
and
you'll,
find
the
group
and
everyone
who
participates
in
that
event
will
be
getting
some
special
swag.
A
B
B
We
call
that
distribution
gitlab
ce
for
community
edition,
that's
licensed
under
an
mit
license.
I
believe,
I
think,
fully
open
source
and
then
get
lab
incorporated.
The
company
also
releases
what
we
call
the
get
lab
ee
distribution
for
enterprise,
and
that
is
a
source
available
proprietary
version.
So
we
take
the
the.
B
Version
of
git
lab
the
ce
edition.
If
you
will,
we
call
that
the
core
of
gitlab,
because
it's
it's,
you
know
kind
of
in
both
and
then
we
add
on
features
that
are
proprietary
to
get
lab
incorporated
on
top
of
that
and
that's
what
we
sell
to
enterprises
and
other
customers
is
that
proprietary
version
of
gitlab
now
the
interesting
thing
about
it
is
it's
also
source
available,
so
the
full
source
of
that
product
right
that
additional
code
that
we
add
to
gitlab
core
is
also
available.
B
F
If
yes,
can
jump
in
with
one
other
component,
I
think
that
was
a
great
overview
and
I'll
just
mention
that,
even
though
there
are
different
distributions,
the
source
code
is
now
just
in
one
gitlab
source
code
repository.
So
it
used
to
be
two
different
repositories
for
there's
a
ce
repository
and
there's
the
e
repository.
Now,
it's
all
just
in
a
git
lab
code,
repository
all
of
the
code
and
the
proprietary
code
is
in
a
different
folder
and
then
the
other
component
is
even
if
you
use
the
ee
distribution.
F
There
is,
if
you
start
out
with
a
community
edition
distro,
and
you
decide
that
you
want
to
upgrade
and
use
some
of
the
paid
features
you
have
to
do
a
complete
migration,
where
you
have
to
switch
to
a
different
code
base,
whereas
if
you
just
start
out
with
the
ee
distribution,
you
can
use
it
without
a
license.
Everything
just
works
and
if,
at
some
point
in
the
future,
you
decide
you
wanted
to
add
some
paid
features,
it's
as
simple
as
adding
a
license
key
and
all
of
a
sudden
those
things
are
unlocked.
B
B
It's
important,
there's
a
there's,
a
lot
that
we've
done
to
talk
about
the
viability
of
open
source
and
the
sustainability
of
open
source
and
open
core
models
and
how
they
work
and
there's
also
a
process
by
which
things
get
moved
down
from
our
proprietary
distribution
into
our
open
source
distribution.
So
recently
we
announced
this
was
a
couple
months
ago
that,
like
18
things
that
we
had
developed
as
proprietary
code,
we
were
actually
moving
into
the
open
source
version
and
the
reason
for
that
is.
B
We
have
a
very
specific
way
of
defining
what
should
go
in
the
proprietary
version,
and
that
should
be
things
that
you
know:
enterprises
that
can
and
should
pay
for
the
software
they
use
will
value
and
and
the
buyers
of
that
will
value.
And
so
we
try
to
make
sure
that
things
that
you
know
developers
need
and
want
get
into
or
start
in
the
open
source
version.
So
that's
something
that's
pretty
unique!
You
don't
see
a
lot
of
open
source
companies.
A
I
love
it
thanks
for
the
great
detail
brendan
and
william.
What
could
have
been
a
one-word
answer.
I
feel
like
just
became
a
really
detailed
explanation,
which
is
great
for
folks
that
are
just
kind
of
getting
up
to
speed
on
some
of
these
different
terms
and
william
thanks
for
pointing
out
the
the
different
kind
of
distributions
being
available
as
a
single
repo
on
the
benefits
to
installing
ee
when
you're
just
getting
started.
A
So
I
just
wanted
to
open
it
up
one
more
time.
We
have
one
more
question
on
the
dock,
and
so
I
want
to
give
folks
in
the
room
a
chance
to
ask
a
question.
You
can
do
it.
You
know
by
verbalizing.
You
can
ask
your
questions
in
the
chat,
if
that's
better,
for
you,
so
I'll
keep
an
eye
on
that,
and
I
don't
see
anyone
on
muting.
So
I'll.
Ask
this
last
question
and
then
we'll
we'll
see
who,
from
the
room,
wants
to
ask
the
next
question.
A
So
this
one's
kind
of
open
ended
alberto
vicente
just
asked
cicd
question
mark,
but
I
wanted
to
ask
this
question
because
we've
been
talking
so
much
about
gitlab
ci
recently
on
our
team.
I
just
wanted
to
see
you
know
kind
of
what's
top
of
mind
for
folks
on
our
team
when
they're
thinking
about
ci,
so
we
could
go
around.
I
don't
know
if,
michael
you
want
to
start
this
one
off.
D
In
my
environments
with
get
libsy,
it's
just.
Oh,
it's
docker,
it's
in
the
sandbox.
It
always
is
the
same.
I
don't
really
care
how
it
works.
It
just
works
and
at
a
certain
level
I
I
also
need
to
like
look
into
how
create
my
own
images,
but
still
everything
is
integrated
smoothly,
and
this
is
what
I
kind
of
like
the
most,
how
how
it
works
and
how
how
easy
it
is
to
like
write
a
short
configuration
and
have
everything
tested.
C
Yeah,
I
think
I'll
summarize
everything
into
the
word
automation.
The
possibilities
are
limitless
right
from
getting
your
code
from
idea
to
production,
to
githubs,
where
you
can
literally
go
from
zero
to
a
full,
fledged
production
and
production
testing
staging
environment
just
from
a
single
push
or
a
match.
So
cicd
makes
possible
almost
anything
you
can
imagine
with
your
code
and
how
you
want
your
infrastructure
or
whatever
it
is
that
you
are
doing
to
be
done.
I
think
I've
seen
people
who
even
do
iot
using
ci
cd
push
some
scripts
gets
deployed.
A
B
Just
add,
john,
in
your
silence,
while
you're
typing
the
answer,
which
is
awesome
yeah
I
mean
I
like
michael
ci-
is
kind
of
what
brought
me
to
get
well,
but
I
came
to
gitlab
as
a
customer
two
ways,
one.
I
came
to
getlab.com
as
a
customer
because
I
was
paying
github
for
private
repositories
for
a
company
that
wasn't
making
any
money
and
gitlab
at
the
time
had
private
repositories
that
brought
me
to
gitlab.com,
but
then
at
a
job.
I
was
working.
B
I
inherited
like,
like
your
traditional
stack,
like
it
was
jira
the
get
lab
to
jenkins
to
nexus
and
artifactory.
For
some
reason,
no
one
could
ever
explain
to
me
why
we
had
both
and
like
ci
was
the
thing
that
really
like
clinched
git
lab
for
me,
both
as
like
a
just
a
personal
hobbyist
user
and
as
a
professional
trying
to
make
things
work,
and
I
think
you
know
a
lot
of
it.
A
B
The
timing
of
when
get
lab
ci
came
to
market
right.
It
came
to
market
at
a
time
when
you
know
docker
had
kind
of
won,
and
you
know
we
were
entering
this
world
where
everyone
understood
the
the
value
of
containerizing
things
and
making.
You
know
the
tools
very
explicit
that
are
in
a
container,
etc
and
like
that
ability
to
just
select
a
container
and
start
building
your
code.
You
know,
and
on
gitlab.com
you
can
do
it
for
free
with.
A
F
I
I
just
appreciate
y'all
letting
me
crash
the
column,
I'm
not
on
john's
team,
but
I
love
everything
that
john's
team
does
so
I'm
over
on
the
product.
Marketing
team-
and
I
just
have
appreciated
enjoying
the
the
conversation
here
and
I'm
excited
that
kubecon
is
going
on
it's
my
favorite
time
of
year.
A
All
right,
so
we
have
one
last
question
in
the
chat
from,
of
course
it
came
from
john
coghill
and
for
folks
that
are
watching
this
later.
There
was
some
kind
of
zoom
bug
where
everyone,
not
everyone,
but
many
of
the
people
who
are
joining
the
room
had
my
name
as
their
display
name.
So
I'm
sorry
to
whoever
submitted
this
question
that
your
name
you're
not
getting
credit
for
it,
but
I
do
appreciate
the
question
and
I
think
it's
a
great
kind
of
way
to
wrap
things
up
because
we're
just
about
out
of
time.
A
So
the
question
is
and
I'll
verbalize
it
since
I'm
the
real
giant
golem.
What
do
you
feel
is
the
most
unappreciated
useful
feature
of
git
lab
and
if
anyone
you
know
it
doesn't
have
to
be
folks
on
my
team.
If
there's
anyone
who's,
you
know
just
a
gitlab
community
member
who
wants
to
shout
out
their
favorite
unappreciated.
Useful
feature
feel
free
to
do
that
so
I'll
see
who
wants
to
unmute
first
and
share
their
favorite
feature.
G
I
would
say
mostly
the
klebsi
ayama,
so
totally
when
the
clip
came
out.
It
was
the
first
direction
into
hey.
We
write
our
whole
the
icd
pipeline
in
a
declarative
way,
so
the
beats
now
currently
some
units
could
be
explode
right
now,
because
we
can
include
other
yammers,
we
can
do
referencing.
We
can
do
a
lot
of
weird
stuff,
but
in
the
end
it
works.
G
D
Yeah,
I
I
would
say-
and
this
reminds
me
of
it-
of
a
discussion
I
had
with
brandon
last
year-
I
think
so
when
I
was
not
working
at
gitlab
but
rendered
it
the
the
issue,
actions
or
you
you're,
defining
an
issue,
template
or
merge,
request
template,
and
then
you
define
the
actions
like
assign
the
issue
set.
The
labels
do
some
other
magic
stuff.
This
is
something
this
is
documented,
but
I
didn't.
D
I
was
not
aware
of
that
right
now,
I'm
using
it
on
a
daily
basis,
because
my
workflows
are
speedy
and
like
when,
when
someone
requests
our
resources
or
something
else,
it's
super
convenient,
but
I
think
not
many,
not
many.
Users
are
aware
of
that
that
this
even
exists
and
how
how
easy
and
how
smooth
this
this
can
go.
In
combination
with
issue
templates
and
much
request
templates.
I
I
would
say:
hi
from
my
side,
I
would
say:
gitlab
ci
parent,
child
pipelines
is
a
really
unlimited,
underestimated
feature
because
it
pops
up
roughly
six
to
12
months
ago.
I
did.
I
found
it,
and
nowadays
I
do
everything
this
parent
child
pipelines,
because
you
can
squeeze
out
so
much
of
your
ci,
which
you
never
expected
before,
because
if
your
projects
get
bigger
or
you
want
more
efficiency,
parent
child
pipelines
are
a
really
awesome
feature
which
is
not
really
discover
able
in
the
beginning,
when
you
start
with
kid
lips,
yeah.
A
B
Yeah,
I
have
two
one
I
think
is
just
the
the
package
registry
in
general,
like
I
said
that
stack
that
I
had
before,
I
was
able
to
start
to
replace
everything
with
git
lab,
except
for
at
the
time
like
artifactory,
and
I
think
the
ability
to
replace
that
and
proxy
other
package
repositories
and
like
actually
store
your
own
libraries
as
packages,
is
going
to
be
a
really
huge
game.
Changer.
As
folks
like
try
this,
you
know
microservices
world
and
intersourcing,
and
all
this
other
stuff.
B
That
sounds
really
great,
but
then
you
have
to
go,
make
work
and
practice.
I
think
the
package
registry
is
an
under-appreciated
useful
feature
in
that
world
and
then
another
one.
I've
got
a
shout
out
to
one
that
I
was
part
of
which
I
don't
even
know.
If
people
will
know
exist,
it's
a
thing
called
visual
review.
Apps
like
raise
your
hand
if
you
knew
know
what
a
visual
review
app
is
awesome.
B
This
is
great
okay,
so
the
idea
of
a
visual
review
app
is
you
can
integrate
a
little
bit
of
javascript
code
into
your
actual
app
and
then,
when
you're
running
a
review
app,
you
can
look
at
the
app
itself
right.
We
all
know
many
of
us
know
about
that.
Right,
gitlab,
spins,
up
a
review
app
automatically
it's
great
and
that's
awesome,
but
with
visual
review
apps,
you
can
actually
then
make
comments
about
it
directly
from
the
app
right
without
having
to
like
switch
between
the
merge
request
and
the
app
itself
so
yeah.
A
Awesome,
yeah
and
I'll
just
give
a
quick
shout
out
to
our
analytics.
There's
lots
of
cool
analytics
that
you
can
look
at
for
different.
You
know
groups
and
repos,
and
it
gives
you
some
great
insight.
At
least
when
your
you
know,
project
is
at
a
certain
scale
to
just
like
the
activity
that's
going
on
and
how
many
merge
requests
are
being
merged,
issues
are
being
open
and
you
can
just
kind
of
keep
an
eye
on.
You
know
the
activity
in
your
project
and
it's
really
cool
visualizations
in
there.
A
So
that
brings
us
to
basically
the
end
of
our
time.
I
thought
I
see
I
just
want
to
make
sure
all
right,
so
there's
no
new
questions
in
the
chat
except
for
brandon's
asking
michelle
something,
but
they
can
follow
there
so
yeah.
I
just
wanted
to
say
you
know
thanks
so
much
everyone
for
participating
today.
This
is
our
first
time
doing
this
and
it
went
much
better
than
I
was
expecting.
To
be
honest,
although
maybe
my
expectations
were
a
little
low.
A
I
really
appreciate
you
know
everyone
who
contributed
to
the
conversation
thanks
for
all
the
interesting
questions
and
interesting
answers
that
you
provided
it's
great
to
have.
You
know
community
member
participation
on
the
call,
so
it
wasn't
just
us
talking
to
ourselves
or
talking
at
you
the
whole
time
and
yeah.