►
From YouTube: GitLab Virtual Meetup Oct 2020 - Best Practices with GitLab CI/CD, presented by Michael Friedrich
Description
We hosted a virtual meetup featuring Michael Friedrich, Developer Evangelist at GitLab, on 2020/10/06.
Title: Best Practices with GitLab CI/CD
Description: Take the first steps in GitLab for your development workflows. Start the first merge request to solve an issue and get ideas on branching, code reviews, approval processes and add automated CI test feedback in MRs.
Repo: https://gitlab.com/dnsmichi/meetup-2020-cw41
Slides: https://docs.google.com/presentation/d/1ajDgQfqNI2TclSpK3DzM8FqNXPSKYHupsDyI3W9bNyo/edit?usp=sharing
---
We would love for you to contribute to our virtual meetups.
You can find upcoming virtual meetups and resources to plan your own here: https://about.gitlab.com/community/virtual-meetups/
We want to hear your ideas for topics. Remote? Security? Contributing to OS? Email suggestions to evangelists@gitlab.com.
We also love when community members present at GitLab meetups. Send an email to evangelists@gitlab.com if you’re interested in being the featured speaker at a future remote meetup.
A
All
right,
hi
everyone
I
just
introduced
myself.
My
name
is
john
coughlin.
I'm
on
the
community
relations
team
at
get
lab
really
excited
to
be
here
today
for
this
meetup,
where
michael's
going
to
show
us
best
practices
in
gitlab
cicd
at
gitlab.
One
of
our
values
is
diversity,
inclusion
and
belonging.
A
A
There's
one
kind
of
conversation,
one
permission
model
we
have
thousands
of
features
always
releasing
on
the
22nd
of
every
month,
so
adding
new
features
all
the
time
and
making
existing
features
better,
and
I
think
you'd
be
really
impressed.
You
know
if
you're,
if
you're
not
familiar
with
gitlab
and
taking
a
look,
a
deeper
look
at
what
we
do,
because
it
can
really
do
a
lot.
A
Some
other
cool
things
about
gitlab,
it's
an
open
core
company,
so
we
have
like
a
free,
open
source
version
that
people
can
use
and
contribute
to.
So
everyone
can
contribute
to
gitlab,
whether
that's
you
know
development
or
documentation,
translations,
organizing
events
for
our
community
speaking
at
meetups,
writing
blog
posts,
there's
lots
of
different
ways.
You
can
contribute
and
if
you're
interested
in
getting
more
involved,
please
you
know
email
that
address.
A
I
shared
evangelisticgitlab.com
or
reach
out
to
me
on
on
twitter
or
michael
on
twitter
we'd
love
to
help
you
get
started
contributing
to
the
community,
some
other
cool
things
about
git
lab,
where
I
used
to
say
we're
the
largest
oil
remote
company
in
the
world.
But
there
are
a
lot
of
all
remote
companies
in
the
world
right
now,
so
we're
the
one
of
the
largest.
You
know
all
remote
companies
in
the
world
and
certainly
the
largest,
that's
always
female
remote
yeah,
and
we
have
really
cool
value
of
transparency.
A
A
So
I
would
encourage
you
to
check
that
out
if
you're,
if
you're
new
to
the
gitlab
community,
as
I
mentioned
earlier,
michael's
going
to
be
walking
us
through
a
best
practices
in
gitlab's,
ci,
cd
workshop
and
demo
today,
so
really
exciting
to
see
that
a
couple
of
small
requests
before
we
get
started
if
everyone
could
keep
their
cameras
on
as
long
as
they're
comfortable
being
recorded.
That
would
be
great.
It's
I'm
sure
michael
appreciates,
seeing
you
you
know,
maybe
laugh
or
not
laugh
at
his
jokes
depending
on
how
good
they
are.
A
It's
also
just
nice
to
see
the
reaction
you
know
of
the
audience
with
some
of
the
cool
things
that
are
going
on
in
his
demo.
Please
keep
your
microphones
muted
unless
you're
going
to
be
asking
a
question,
as
I
mentioned
earlier,
be
awesome
and
folks
could
share
where
they're
joining
from
in
the
zoom
chat.
So
we
get
a
sense
of
you
know
the
kind
of
scope
or
size
of
our
global
community.
A
If
you're
going
to
tweet
about
the
meetup
use,
hashtag
gitlab,
meetup
and
also
put
michael's
twitter
handle
in
the
zoom
chat,
since
I'm
sure
he'd
be
very
happy
to
see
a
lot
of
tweets
about
how
great
his
sock
was
or
not
great,
depending
on
how
it
goes
and
yeah
the
last
thing,
just
you
know
close
your
tabs
mute,
slack,
relax
and
and
try
and
be
present,
because
this
is
going
to
be
a
really
cool
presentation
today.
So
without
further
ado,
here's.
B
B
B
So
the
first
thing
I'm
gonna
do
here
is
I'm
sharing
the
slides
with
you
and
I'm
inviting
you
to
follow
up
the
slides
and
the
exercises,
especially
because
there
will
be
some
which
you
can
practice
at
home
later
on.
So
let's
just
start
over
here
short
in
trip
short
overview
in
the
agenda.
We
do
a
short
introduction,
the
first
steps
with
ci
cd.
B
B
B
Before
that,
I
was
working
quite
a
long
time
in
the
monitoring
area,
and
I
found
it
really
convenient
really
nice
to
follow
the
everyone
can
contribute
storyline
when
I'm
not
engaging
on
any
social
media
channels.
You
might
find
me
on
a
building
a
new
lego
model
or
something
else
around
it
or
just
enjoying
the
nuremberg
area,
the
countryside,
with
that,
let's
start
over.
Let's,
let's
dive
into
the
workshop,
just
some
preparations
in
case
you
want
to
like
continue
working
on
the
exercises
with
me.
Now
you
need
a
gitlab.com
account.
B
B
I've
shared
the
url
for
the
presentation
in
the
zoom
chat
already.
If
you
cannot
follow
it
or
I'm
just
talking
too
quickly,
which
can
happen,
you
can
do
the
exercises
asynchronously,
so
they
are
self-contained
and
if
you
want,
you
can
also
use
the
slides
or
exercises
for
your
own
workshops
for
your
own
meetups
be
inspired
just
repurpose
the
content,
it's
free
for
everyone,
and
it
should
be
easy
to
learn
about
gitlab
so
for
the
first
steps
with
gitlab,
ci
cd
you're,
probably
aware
of
that
or
you
maybe
have
heard
of
of
it.
B
When
you
start
working
on
a
new
feature,
you
probably
get
an
issue
assigned
you
create
some
commits.
You
work
in
a
feature
branch.
You
create
a
merge
request
and
then
you
commit
your
changes
and
in
the
best
way
you
have
some
sort
of
automated
test
runners
and
also
ci
jobs,
continuous
integration
shops,
which
help
build
your
application,
maybe
even
some
security
scanning,
and
it
goes
on
with
your
apps
staging
deployments
and
so
on.
B
B
We
want
to
define
a
test,
simple
drop
on
the
on
the
top
level.
This
is
the
job
name
and
we
want
to
execute
a
script
which
actually
executes
exit
one
with
that
just
saying
test
simple
and
it's
super
convenient,
because
the
two
spaces
are
automatically
transformed
by
the
web
id.
I
want
to
execute
a
script,
and
then
I
want
to
execute
exit
one.
B
The
next
step
is,
I
want
to
actually
run
that
and
before
doing
so,
I
need
to
commit
the
change.
I
say:
okay,
I'm
adding
a
ci
configuration
and
I'm
committing
this
to
see
the
ci
test
branch.
I
also
want
to
create
a
merge
request
to
see
everything
highlighted
in
there
and
I
can
assign
it
to
myself.
I
can
design
a
milestone
labels
and
so
on
right
now.
I
just
want
to
commit
that.
B
I
submit
the
merge
request
and
I
can
see
that
the
pipeline
is
has
already
been
started
when
I
click
on
that,
I
can
navigate
into
the
pipeline
overview
and
I
can
see
oh
in
this
case
it
failed.
So
the
the
question
is:
why
does
it
fail
and
I
can
go
inside
the
job
view
get
an
idea
what's
going
on,
so
the
gitlab
runner
is
starting
up.
It's
pulling
the
docker
image
which
we
defined.
Previously
it
does
some
preparation
steps
and
then
it
executes
exit.
B
B
B
B
This
was
actually
this
example,
and
we
also
did
a
deep
dive
into
this
one
already.
So
the
next
step
would
be
to
dive
a
little
further
and
say
hey
when
I
want
to
add
certain
pyramid
parameters
or
instructions
to
to
jobs.
I
can
influence
that
with
environment
variables
from
the
ci
job,
so
one
example
would
be
to
define
the
variables
entry
and,
for
example,
define
the
build
type
name.
It
give
it
a
value
called
release
and
then
print
it.
C
B
B
B
You
might,
for
example,
import
specific,
open
source
project
or
project
from
svn
from
from
different
kit
repositories,
and
you
don't
know
if
it
builds.
It
has
never
seen
any
ci
cd
system
before
yeah
and
it's
just
unclear.
What's
going
on,
and
one
of
the
first
things
I
normally
do
is
when
I
get
some
code
where
it's
unclear
to
me
how
it
works,
I
kind
of
inspect
it.
I
read
it
and
when
analyzing
it
I
say:
okay,
it's
it's
go
code,
for
instance,
and
I
want
to
add
a
ci
cd
config.
B
B
We
can
actually
reuse
the
built-in
gitlab
cicd
templates
for
that.
So
when
we
are
navigating
back
to
the
web
ide,
we
are
in
this
case
adding
a
new
gitlab
ci
file.
We
can
just
say
I
want
to
use
a
template
and
I'm
searching
over
here
for
go
just
picking
go
and
this
generates
what
just
imports
the
template.
For
me.
I
need
to
do
some
some
changes
in
there.
One
is
setting
the
variable
name,
the
variable
wrapper
name
to
the
name
of
the
repository.
B
B
I
want
to
change
my
binary
to
tanuki,
because
actually,
what
we
are
going
to
build
is
something
tanooki
related
which
we
will
be
executing
later
on
and
with
that
just
looking
at
it,
we
have
added
the
first
ci
configuration
and
we're
gonna.
Add
this
to
the
ci-config
branch
and
we'll
create
the
mesh
request.
B
The
ci
jobs
should
have
been
started
and
when
we
navigate
over
here,
we
can
see
changed
a
bit.
We
have
a
test
stage
where
the
format
is
being
run
on
and
then
there's
a
build
stage
which
compiles
the
source
code.
Let's
just
peek
in
there,
okay,
the
docker,
the
docker,
execute
the
image,
pull
is
taking
a
little
longer.
B
The
thing
is,
it
might
build
the
go
code
now
or
it
might
not.
Let's
just
see
what's
going
to
happen
and
doesn't
look
that
good,
so
the
steps
it
basically
does.
It
prepares
the
environment,
it
does
some
formatting
checks
and
then
it
tries
to
build
the
code
and
it
says:
well,
there
is
an
undeclared
name
and-
and
I
probably
will
missing
a
package,
so
the
thing
is
format.
Job
should
be
yeah,
the
format
shop
failed
and
therefore
the
build
drop
did
not
execute
yet
so
I
need
to
fix
it.
B
This
one
is
the
first
failing
iteration,
and
this
one
is
the
second
one
I
need
to
import
the
packages
and
just
to
to
to
make
it
more
convenient
without
typing
that
much.
I
can
just
import
that
just
I'm
commenting
it
again
and
we're
gonna
fix
the
build,
not
the
best
git
commit
message,
but
actually
this
is
what
we're
gonna
do
now
again.
B
B
If
you,
if
you
do,
have
problems
with
slow
runners
or
just
slow
job
execution,
we
also
have
edited
new
documentation
for
ci
efficiency
or
pipeline
efficiency,
which
is
also
linked
in
the
slides,
and
we
can
see
okay,
the
build
succeeded
and
it
should
have
triggered.
This
is
something
I'm
navigating
back.
It
now
should
attempt
to
build
the
girl
code,
which
again
happens
in
a
separate
job
in
a
separate
sandbox
environment,
just
just
yeah,
sandbox,
environment,
the
container
environment
and
you
get
the
reliable
resource
every
time.
B
So
it's
basically
the
same
environment
to
run
the
jobs
all
the
time.
Okay
and
if,
for
example,
the
cloud
runners
are
slow,
you
can
also
install
your
own
gitlab
runners
in
your
own
virtual
machine,
be
it
in
aws
or
somewhere
else
and
connect
it
to
the
gitlab.com
account
or
you
do
a
self-hosting
which
allows
you
to
put
it
on
harder
and
not
on
harder
on
stronger
hardware
as
well,
and
as
we
can
see,
we
have
built
the
files
now
and
it
actually
created
an
artifact
which
is
called
tanooki.
B
It
on
a
linux
host,
because
this
is
a
golan
binary
right
now
on
mac
os,
I
will
be
having
problems,
but
one
could
make
that
happen
in
a
sense
of
making
this
happen.
We
actually
want
to
run
the
generated
binary
ourselves
within
the
ci
job,
just
to
see
what's
the
output,
what
are
the
tests
being
run
and
and
so
on?
B
So
in
order
to
achieve
that,
we
can
edit
the
gitlab
ci
yammer
file,
and
we
can
see
we
have
a
deploy
stage
over
here
as
well,
so
the
format
is
being
run
at
the
test
stage.
The
compile
job
is
being
run
in
the
build
stage,
and
last
but
not
least,
we
want
to
define
our
own
rank
job,
which
runs
in
the
stage
deploy
and
the
script.
B
B
Did
it
change
already
yeah?
Something
is
going
on
yeah
it
took
a
while
now
we
can
see
there's
a
another
job
inside
and
we
do
run
again.
So
it's
in
it's
kind
of
a
gamification
and
it's
an
iterative
process
involved,
and
I
would
advise
you
to
plan
some
time
on
getting
things
started,
trying
things
things
out,
especially
because
I
would
say
the
perfect
pipeline
doesn't
exist
and
yeah
another
thing
which
can
be
added
or
should
be
added.
B
When
you
are
creating
code
work
statements
for
unit
tests,
you
can
also
tell
gitlab
to
pass
the
output
for
the
test
coverage.
This
can
be
done
within
the
settings
for
ci
cd
and
the
general
pipeline,
and
it
says
test
coverage
parsing
to
the
go
example.
So,
for
example,
in
my
project,
where
I
need
to
navigate
into
my
settings
and
ci
cd
I
do
have
where
is
it?
Was
it
general
pipelines?
B
B
C
B
And
I
want
to
copy
paste
this
into
the
pipeline
is
being
run.
The
pipeline
is
being
run,
perfect,
short
contact
switch,
we
did
run
the
pipeline
and
yeah
we
can.
We
can
see
that
the
tanuki
has
been
summoned.
So
if
you,
if
you
are
seeing
that
it's
success,
you
can
skip
everything
else.
No,
this
is
this
should
be
possible
with
inspecting
the
tanuki
dot
gold
code
and
the
thing
I
wanted
to
show
you.
B
We
do
have
the
merch
request,
which
is
this
one
and
we
open
up
the
web
ide
once
again
and
we
do
have
the
tanuki
code
over
here.
We
have
some
test
functions
over
here,
so
this
is
basically
a
little
bit
deep
down
everything
which
gets
bit
gets
tested
and
for
the
unit
test
code
and
I'm
running
out
of
time
a
little.
I
just
want
to
add
this
one
over
here
and
in
the
sense
in
the,
in
the
hope
that
this
is
the
correct
yaml
syntax.
B
B
If
you
want
to
call
it
like
that
and
then
gitlab
pauses
that-
and
we
can
actually
see
that
in
the
merge
request
or
in
the
output
of
the
pipeline
again,
this
now
takes
a
little
while
and
while
it
takes
a
little
while,
oh
it
doesn't
act.
Actually
it
was
pretty
fast.
We
can
see.
73.5
percent
of
statements
are
being
covered
if
you
change
that
or
if
you
add
functions
later
on,
which
do
not
add
any
test
test
code.
B
This
decreases
over
time,
and
this
is
a
way
of
inspecting
this
and
checking
checking
it
during
code
reviews,
for
instance,
to
ensure
that
tests
are
being
written
and
everything
is
everything
is
awesome.
Basically,
so
now
I've
been
hopping
too
much
between
things.
Let's
just
go
over
here
again
and
yeah.
I
was
about
to
say
that
you
can
run
the
unit
test
on
each
commit
push
or
merge
request.
It's
basically
fully
integrated.
B
These
events
trigger
trigger
that
you
should
be
able
to
add
test
coverage.
You
can
dive
even
more
into,
for
example,
check
unit
integration
which
grants
you
the
nice
overview
about
the
tests
inside
the
pipeline
view,
so
you
can
actually
see
how
many
functions
are
being
tested
and
how
often
this
failed
and
so
on,
and
the
code
reviews
or
the
the
entire
review
process
should
be
starting
once
the
tests
are
completed.
So
when
something
fails,
it
doesn't
make
sense
to
start
a
review.
B
B
The
next
few
slides
are
for
self-practice,
so
I'm
leaving
you
or
giving
you
a
little
home
exercise
now,
having
heard
about
the
junit
integration,
I've
prepared
an
example
in
the
gitlabciar.org.yaml
file,
and
this
is
a
kind
of
a
pre-compiled
exercise
with
everything
you
need
you
would
need
to
type.
Otherwise
you
can
add
a
new
function
integrated
see
that
the
test
coverage
decreases
and
later
on.
You
fix
it
by
adding
a
new
test.
B
This
is
prepared
in
the
repository
as
well
and
last
but
not
least,
I
want
you
to
try
it
out
about
the
test
coverage
and
pipeline
status
batches.
So
you
can
add
that
directly
into
your
gitmap
project
and
when
you're
done
with
that,
I
want
you
to
take
a
screenshot
of
what
you
did
and
tweet
it
to
me.
Please.
B
And
with
that
what's
next
last
slide,
this
was
lots
of
things
about
ci
cd
covers
things
or
topics
where
I
would
prob.
This
would
probably
take
me
or
take
us
one
week
to
discuss
everything
or
dive
through
you
should
look
into
environments
with
staging
and
production
environments,
look
into
review
apps,
getting
an
idea
what
it
does:
github's
monitoring
and
security,
and
last
but
not
least,
and
I'm
kind
of
clicking.
C
Yes,
thank
you,
so
I
I
noticed
through
each
step
of
the
job
that
there's
a
a
docker
image
pool
and
I
wanted
to
know
if
there's
a
way
to
cache
between
steps
so
that
that
docker
image
pool
is
just
the
same
one
used
between
steps.
So
it's
saving
time
and
consumption
and
cpu
consumption
for
this.
For
the
gitlab.
B
I
don't
know
if,
if,
if
you
can
really
cache
it
when
when
the
job
is
being
run
because
it's
really
starts
a
new
environment,
one
thing
you
can
do
is
right
now
I've
been,
I
think
I've
been
pulling
from
docker
hub
all
the
time.
I
have
to
be
honest.
I
don't
know
exactly
how
gitlab.com
is
configured
in
the
background.
B
One
thing
you
can
do
is
put
the
docker
registry
into
gitlab
because
you
can
use
the
package
registry
and
you
have
it
side
by
side.
So
the
gitlab
runner
actually
has
a
low,
has
zero
latency
to
the
registry,
and
you
can
also
try
to
optimize
the
docker
image
size,
for
instance.
So
sometimes
you
might
end
up
with
one
gigabyte
of
docker
image
files,
because
it's
all
in
one
package
for
every
job
you
could
imagine
it
makes
sense
to
to
optimize
docker
images.
B
This
is
also,
I
think,
one
portion
of
one
part
of
optimizing,
docker
image
of
the
documentation.
I've
just
shared
yeah
and
I
think
the
registry
has.
It-
has
a
way
to
cache
images
which
are
pulled
quite
often.
So
it's
not
it's
not
pulling
everything
from
the
internet
without
any
job.
Again
I
said
the
gitlab
registry
is
enabled
by
default
and
should
be.
C
B
B
So
it's
also
a
good
idea
to
consider
building
your
own
docker
images
or
ci
job
images.
Whatever
you
want
to
call
it
and
store
them
within
your
self-hosted
gitlab
registry,
then
so
you
don't
have
any
network
traffic
involved
and
also
no
latencies
in
docker
login
docker
pull
over
the
internet
into
the
cloud.
A
Hey
michael
I'll,
ask
you
a
question
since
it,
even
though
we're
on
the
same
team-
and
I
can
ask
you
any
time
you
know.
One
thing
I
noticed
you
know
is,
as
you're
kind
of
you
know,
adding
functionality
to
the
ci
yaml.
The
kind
of
pipeline
like
readout
gets
longer
and
I
feel
like
that's
something.
You
know
that
I
struggle
with
at
gitlab.
We
have
like
a
very
large
ci
pipeline,
and
so
the
kind
of
you
know
error
messages
and
things
can
be
hard
to
discern.
A
B
B
B
B
One
way-
and
this
is
something
I
recently
learned
as
well-
you
can
like
hide
that,
as
you
maybe
know
from
an
ide
or
you
can
hide
code
blocks,
and
sometimes
I'm
just
like
hiding
everything
I
don't
need,
but
most
of
the
times
it's
just
searching
for
an
error
or
there's
a
specific
pattern
like
when
you're
developing
c,
plus,
plus,
you
might
see
stack
traces
with
ruby.
You
have
some
sort
of
also
stack
traces,
exception,
handling
python.
B
B
I
get
the
file
name,
I
get
the
line
number
and
I
get
the
character
number.
So
I
this
would
be
super
nice
if
it
could
just
link
and
click
on
it.
Probably
I
should
open
a
feature
request
for
that,
but
in
the
end
I
can
analyze
that-
and
I
don't
know
if
I
have
any
other
examples,
but
for
example,
for
for
gitlab.com
for
the
blog,
we
also
it
with
gitlab
ci
cd,
and
sometimes
there
is
a
ruby
exception
inside
which
is
totally
unreadable
and
it
just
takes
the
whole
page.
B
Basically,
and
then
it's
our
goal
or
our
idea
to
improve
that
and
say
hey,
we
developers,
we
totally
need
the
stack
trace.
We
want
to
analyze
what's
going
on
and
how
to
debug
it,
but
if
someone
else
is
being
on
call
or
wants
to
like
look
into
that,
we
need
to
cut
it
down
and
make
it
a
short
error
message
and
say:
hey
by
the
way.
It's
missing
an
import
or
the
yammer
configuration
for
the
back
end
is
wrong.
Please
consult
the
troubleshooting
documentation
by
the
way
the
url
is
over
there.
B
B
B
B
This
is
actually
just
what's
written
inside.
So
the
parser
of
the
ci
configuration
collects
all
the
expressions
all
the
includes
and
builds
asd
whatever
in
the
background,
basically
all
the
objects,
and
this
is
being
run
so
this
can
be
super
convenient
and
you
can
abstract
it
and
one
thing
for
security
and
other
things
is.
B
You
can
also
leverage
that
and
provide
a
central
repository
where
all
the
best
practices,
for
example,
are
being
stored
for
the
ci
templates.
You
want
to
keep
using
just
for
checking
specific
formats
or
tests
or
other
things
and
yeah.
This
is
something
you
can
do
and
should
do,
and,
as
nicholas
mentioned,
you
can
also
include
local
files.
I
think
what
I
just
did
is
the
short
iteration
of
the
short
version
of
including
a
local
file.
I
was
just
being
lazy,
but
you
can
also
include
remote,
remote
files.
B
B
I
can
use
a
file
from
a
different
project
repository
or
even
from
a
remote
file,
and
the
templates
are
those
being
provided
by
gitlab
itself.
This
also
covers
certain
static
application,
security,
dynamic
application,
security
templates
which
are
used
for
secret
scanning
dependencies
scanning
security
scanning
and
so
on,
and
everything
which
you
can
see
in
the
auto
devops
ci
cd
templates
as
well.
B
B
A
Up,
okay,
I'm
not
seeing
anything
in
the
chat,
so
one
thing
I
like
to
do
at
the
end
of
meetups
is
ask
folks
to
unmute
their
microphones
and
just
give
our
speaker
a
round
of
applause.
So
if
you'll
join
me
and
say,
thank
you
to
michael
great
job
today,
michael,
very,
really,
good
presentation.
You
definitely
were
flying
through
that.
I
was
impressed
that
you
were
able
to
to
cover
so
much
and
stay
organized.
So
thank
you
for
the
preparation
and
for
delivering
a
great
session
today
for
folks.
A
You
know
that
do
have
follow-up
questions.
I'm
gonna
put
my
email
address
back
in
the
chat
box
again,
evangelistickitlab.com
feel
free
to
reach
out
with
any
follow-up
questions
that
you
have
or
reach
out
to
to
michael
on
social
media.
I'm
sure
he'd
be
happy
to
hear
from
you
on
twitter
and
I
just
wanted
to
give
like
a
little
psa
for
these
virtual
meetups.
A
You
know
we
really
love
kind
of
being
able
to
connect
with
our
community,
and
these
virtual
meetups
are
a
great
way
to
do
that
during
these
kind
of
you
know
covet
days.
So
we
expect
to
keep
doing
this.
For
for
the
long
term,
and
would
love
for
all
of
you
to
continue
participating
and
attending
the
meetups.
If
folks
are
interested
in
being
a
speaker
or
doing
a
presentation
like
michael
did
today,
we'd
also
love
to
hear
from
you.
A
We
think
it's
really
great
when
our
community
gets
involved
and
and
kind
of
shows
how
they're
using
gitlab
and
cool
and
interesting
ways.
So
definitely
let
me
know
again
by
using
that
email
address.
That's
in
the
zoom
chat,
if
you're
interested
in
speaking
at
an
upcoming,
meetup
and
yeah.
You
know,
if
you
have
you
know,
feedback
or
kind
of
topics
that
you'd
like
to
hear
about
or
other
suggestions
for
how
we
can
make
the
meet
ups
better.
B
I
just
want
to
add:
I
can
help
you
create
workshops
and
presentations
for
your
own
events,
so
just
reach
out
to
me
I'm
happy
to
share
my
slides.
We
can
also
translate
it
to
french
or
to
spanish.
I
don't
speak
it,
but
we
can
make
it
happen.
It
should
be
possible
to
just
make
it
easy
to
learn
everything
and
it
should
be
free
for
everyone.