►
From YouTube: GitLab Student Contributor Workshop | City University of Seattle - Google Developer Student Group
Description
This is a recording of the first iteration GitLab Student Contributor Workshop for the City University of Seattle - Google Developer Student Group.
A
All
right,
hello,
everyone
welcome
to
the
get
lab
student
contributor
workshop
here
at
cityu
seattle.
We're
very
excited
to
be
here
to
chat
with
you
about
today
about
contributing
to
open
source
and
then
we're
also
gonna
use
the
example
of
contributing
to
gitlab.
So
we're
excited
I'm
christina
huppy.
I
am
a
manager
of
education
programs
here
on
the
community
relations
team
at
get
lab
and
we
also
have
pj
pj.
Would
you
like
to
say
hello.
B
And
to
find
the
unmute
button,
yeah
I'd
love
to
say,
hello,
hi,
I'm
pj,
metz
education,
evangelist
from
git
lab.
I
am
excited
to
be
here.
I'm
excited
to
be
a
part
of
this
team
and
working
to
bring
devops
into
classrooms
and
into
students
lives
across
the
world.
So
thank
you
for
having
me
here
and
having
christina
here
and
having
us
here
and
yeah
back
to
you
just
you
know,
quick,
quick
introductions
today,
quick
introduction.
A
A
A
Source
get
my
queue
here,
so
we're
going
to
talk
a
little
bit
about
what
open
source
is
and
then
why
consider
contributing
to
an
open
source
project,
I'm
going
to
share
some
open
source
projects
that
are
actually
hosted
on
gitlab.
We
have
dozens
of
really
cool
projects
that
are
hosted
on
gitlab
itself
and
then
we'll
talk
about
how
you
can
contribute
to
git
lab
the
open
source
project.
So.
C
A
B
A
And
it's
also
a
platform,
the
devops
platform,
but
then
it's
also
an
open
core
project.
So
we're
an
open
core
company
and
the
core
of
what
we
do
is
open
source.
And
so
we
welcome
contributions
from
all
kinds
of
community
members
and
we'll
talk
a
little
bit
about
that
and
then
pj
and
I
are
going
to
go
through
a
demo
of
how
you
can
actually
contribute
and
we'll
do
that.
Live
and
we'll
show
you
how
to
do
that
and
then
we'll
kind
of
break
into
a
workshop
where
students
can
try
to.
A
A
We
always
like
to
share
a
little
bit
of
our
gitlab
community
code
of
conduct,
and
I
don't
need
to
read
it
word
for
word
here,
but
basically
we
really
want
to
foster
an
open
and
welcoming
environment
for
all
of
our
contributors
and
maintainers,
and
anyone
in
our
community
really
and
we
want
that
to
be
a
welcoming
and
harassment
free
experience.
Regardless
of
your
background
at
all,
and
so
I
you
know
pj,
if
you
don't
mind,
grabbing
the
link
and
putting
it
in
the
chat
there
to
our
community
code
of
conduct.
A
A
Part
of
contributing
to
open
source.
You
want
to
make
sure
that
any
of
the
projects
that
you
contribute
have
a
community
code
of
conduct
so
that
it
is
a
welcoming
and
inclusive
environment
and
that's
something
that
we
really
strongly
value
at
gitlab,
diversity,
inclusivity
and
belonging
is
one
of
our
values
and
we
extend
that
throughout
our
community.
So
we
wanted
to
take
a
time
to
visit
that.
A
The
mit
license
there's
a
couple
other
different
kinds
of
licenses:
we're
not
going
to
get
into
the
details
of
what
the
actual
license
does,
but
just
each
one
has
different
guidelines
and
and
rules
for
kind
of
how
to
distribute
and
edit
the
software.
That's
so
that's
an
important
thing
to
just
kind
of
kind
of
be
aware
of
it's
a
pretty
pretty
interesting
topic.
A
Our
code
maintainers
are
employees
of
gitlab,
so
they
work
at
get
lab
and
they
take
contributions
from
people
in
the
wider
community.
If
the
open
source
project
is
not
also
a
company,
you
say
it's
just
more
of
a
volunteer
community
than
it
may
be
volunteers
who
are
who
who've
kind
of
achieved
the
maintainer
status?
Who
will
help
merge
code
in
so
it
just
it
really
kind
of
depends.
A
Like
I
mentioned,
the
code
is
kept
your
repositories
online
and
get
the
technology
that
does
the
version.
Control
is
a
really
important
component
of
that
right,
because
it
allows
us
to
store
data
and
code
in
a
central
repository
and
make
make
changes
and
keep
track
of
those
changes,
and
in
this
central
repository,
discussions
can
take
place
between
the
contributors,
the
maintainers,
the
owners
and
then
also
the
users
of
the
code
as
well.
A
A
But
a
lot
of
communities
will
have
things
that
are
good
for
new
contributors,
and
we
have
that
at
gitlab
and
the
example
that
we're
going
to
talk
about
today
is
just
editing
text
files,
the
demo
that
we're
going
to
give
is
editing
text
files,
and
so
just
because
you
may
maybe
not
have
a
super
in-depth
technical
experience.
If
you're
early
in
your
you
know
your
software
development
or
computer
science
degree,
you
know,
there's
still
ways
you
can
contribute
and
documentation
is
a
really
good
example
of
that.
A
A
It's
your
own,
your
own
schedule.
I
think
it's
also
really
cool
to
think
about
it
as
a
way
to
build
your
technical
portfolio.
So
you
know,
I
think
everyone
gets
their
minds
out
as
their
students.
I
don't
have
to
get
this
internship
or
you
know
I
want
to
go,
get
you
know,
get
into
that
program
or
that
prestigious
thing
and
that's
you
know,
there's
only
so
many
slots,
sometimes
there's
geographic
barriers,
sometimes
there's
time
barriers,
sometimes
there's
other
problems.
A
You
know
other
challenges
and
so
open
source
contributing
to
open
source
is
a
great
way
to
to
build
your
portfolio.
Think
of
it
as
like
a
project
that
you
work
on
in
a
class,
you
could
work
on
a
project
for
an
open
source.
You
know
an
open
source
project
and
have
that
be
that
you
know
fill
that
same
kind
of
purpose.
So
it
also
builds
a
public
record
of
your
contribution.
A
A
Who
are
creating?
You
know
the
ideas
for
contribution,
you're
meeting
the
people
who
are
also
reviewing
your
code
and
mentoring
you.
So
it's
a
great
way
to
build
your
network,
and
the
experience
translates
to
other
things
right,
so
it
translates
to
on-the-job
experience
working
with
classmates
working
with
your
professors.
Working
with.
Maybe
you
know
in
a
research
team
or
whatever
it
is
that
you're
doing
those
skills
aren't
transferable
right.
So
it's
not
like
it's
happening
in
a
vacuum.
It's
things
that
you're
building
your
to
your
portfolio.
D
A
A
So
when
you're
considering
contributing
to
an
open
source
project,
some
things
to
consider
availability
of
onboarding
help
issues
for
first
time
or
new
contributors
and
then
communication
channels.
So
maybe
they
have
a
forum
pj.
If
you
don't
mind
sticking
the
link
in
the
chat
to
our
get
lab
forum,
that
would
be
helpful
and
then
we
also
have.
A
A
D
A
Go
ahead
and
click
on
this
link,
and
this
shows
you
a
list
of
some
of
our
open
source
projects
here
and
I'm
gonna
go
ahead
and
stick
that
in
the
chat
as
well,
and
so
this
table
gives
you
some
examples
that
might
be
a
little
small.
So
let
me
try
to
zoom
in
there
a
little
bit,
but
here's
a
list
with
with
hot
links.
So
these
are
all
projects
that
are
hosted
on
git
lab
that
that
you
could
consider
checking
into
and
contributing
to.
So
it's
a
really
good,
pretty
good
list.
A
You
may
you
know
recognize
some
words
on
here
like
linux,
a
couple
different
linux
linux
projects.
Drupal
is
another
name
that
you
may
that
you
may
recognize.
So
we
encourage
you
to
take
a
look
at
this
list
and
just
kind
of
poke
around
and
see
what
what
interests
you
and
maybe
take
a
look
at
like
do
they
have
a
community
code
of
conduct?
Do
they
have
issues
for
new
contributors?
A
You
know
was:
is
there
something
in
their
tech
stack
that
you've
been
learning
that
you
would
love
to
be
able
to
add
your
portfolio?
And
you
could,
you
know,
take
some
time
over
the
summer
or
your
break
and
see
if
you
can
kind
of
make
some
progress.
You
know
on
learning
some
of
these
different
things
oops
like
don't
you
have
there?
A
The
other
thing
I
wanted
to
show
you
is
that
we
at
gitlab,
we
have
an
open
source
program
where
we
provide
free
ultimate,
which
is
our
top
tier
licenses
to
open
source
projects
that
qualify.
There's
a
couple
qualifications,
I'm
not
going
to
get
into
the
details
there,
but
for
those
that
are
want
to
host
their
community
and
get
lab
and
then
encourage
their
their.
You
know
contributions
to
happen.
A
We
have
the
get
lab
open
source
partners
program,
I'm
just
gonna
scroll
down,
because
you
might
recognize
some
of
these
other
logos
here.
So
gnome
is
another
one.
Freedesktop.Org
debian
arm
phenos
drupal
arch
linux
fedora.
These
are
these
are
ones
that
you
may
recognize,
so
these
are
kind
of
special
special
special
open
source
projects
that
we
have
a
relationship
with.
So
I
encourage
you
to
take
a
look
at
that
list
as
well,
and
I
I
do
want
to
mention
a
little
bit
about
our
code
contributor
program.
A
Anyone
who's
using
gitlab
right
any
developer,
any
user
of
gitlab
can
make
it
a
contribution
and
then
it
kind
of
gets
more
specialized
from
there.
So
we
have
customers
who
contribute
to
gitlab
because
they
want
a
certain
feature
that
maybe
is
unique
to
their
use
case
or
you
know
they've
developed
on
their
own
and
they
they
think
other
people
might
want
to
use
it.
So
they
might
want
to
put
it
back
in
our
core
and
so
there's
a
whole
bunch
of
different
reasons.
A
A
A
So
where
can
you
contribute
to
gitlab
if
you're
interested
well,
there's
a
couple
different
ways,
and
we
don't
have
time
to
get
into
all
of
these
in
too
much
detail,
but
I'm
going
to
point
out
a
couple
and
one
of
them
I
already
mentioned,
which
is
documentation
right.
So,
let's
just
say
you
don't
have
a
ton
of
you
know
tools
in
your
stack
yeah,
but
you
still
want
to
get
started.
Technical
writing
is
a
great
way
to
do
that.
We
also
have
translation
opportunities.
A
A
Is
more
like
front
end
versus
back
end,
so
development
is
more
back
end
and
then
front
end
is
going
to
be
the
user
experience
and
then
there's
things
like
contributing
to
templates.
So
we
use
templates
issue
templates.
All
the
time
to
ci
cd
templates
are
another
great
example,
so
there's
ways
to
contribute
without
that
high
technical
bar
and
then
we
have
ways
to
contribute
our
in
our
community,
so
you
can
host
a
meetup.
A
You
can
write
a
blog
post.
We
would
love
to
hear
about
your
experience
as
a
student
contributor.
If
you
post
it
on
your
blog,
you
know
we
can
share
it
that
kind
of
stuff
and
then
our
handbook,
and
then
we
also
have
the
example
of
a
linter
which
is
where
you
search
through
our
handbook
or
search
through
our
documentation
for
certain
phrases
or
typos,
and
then
you
can
identify
ways
that
you
want
to
fix
those.
So
I'm
going
to
click
on
this
link
for
development.
A
A
Great
opportunity
to
connect
with
professionals
come
hop
in
a
zoom
call
and
meet
some
front-end
developers
and
ask
questions
about
contributing
to
gitlab.
It's
it's
a
great
way
to
get
involved
in
the
community,
so
I'm
gonna
go
ahead
and
post
this
link
in
here
as
well,
so
that
you
can
see
it.
But
this
is
a
guide
about
contributing
kind
of
to
the
back
end
and
it
walks
you
through
finding
an
issue
or
project
to
contribute
to.
A
A
A
A
I
think
pj,
and
I
found
that
last
time
we
kind
of
looked
at
some
of
the
background
stuff.
You
know
we
use
a
lot
of
ruby
on
rails,
and
so
you
want
to
check
into
that
tech
stack
to
see.
If
there's
you
know,
tools
that
that
are
in
your
stack
that
you're
comfortable
with
otherwise
again
we
recommend
kind
of
starting
back
out
at
this
documentation
of
my
book.
D
A
Think
of
this
from
a
software
development
perspective
right,
you're,
you're
planning
what
you're
gonna
you
know
in
issues
and
epics
and
and
those
labels
and
milestones
you're
gonna
plan
what
you're
gonna
develop.
Then
you
write
the
code
and
then
you
move
through
verifying
it
packaging
it
sending
it
out
there
making
sure
it
works.
Getting.
A
To
work
and
then
monitoring
it,
and
so
this
is
all
kind
of
really
happening
in
you
know
in
one
one
place,
which
is
the
benefit
of
working
in
a
single
devops
platform,
is
that
we
find
our
customers
and
our
community
can
develop
so
much
faster,
which
is
a
huge
benefit
for
open
source
projects.
Right
because,
if
you're
trying
to
get
contributors
to
to
help
your
project
grow
and
they
have
to
use
10
different
things
and
they
have
to
log
in
and
configure
it
all
the
work
together.
D
A
Like
right,
if
you
were
to
come
to
contribute
to
get
lab,
you
would
find
you
know.
Product
manager
would
create
an
issue
and
say
hey.
This
is
a
good
issue
for
a
community
contribution
and
then
you
would
basically
take
that
issue
and
make
a
make
a
merge
request,
a
branch
off
the
main
branch,
and
then
you
would
commit
your
changes.
A
You
would
have
your
ci
pipeline
run
review
kind
of
what
you
did
and
then
you
would
assign
it
back
to
a
git
lab
maintainer
and
and
that's
all
in
the
directions.
It
shows
you
how
to
you
know
how
to
find
the
maintainer
for
where
what
you're
working
on
and
usually
it's
in
the
issue.
So
it's
not
that
hard.
But
let's
say
there
wasn't
an
issue.
You
found
something
you
wanted
to
create.
You
can
find
the
maintainer
of
that
part
of
the
product
and
then
there's
some
peer
review
and
discussion.
A
A
And
I'm
gonna
just
go
ahead
and
get
lab
handbook.
I'm
gonna
go
ahead
and
google
that
and
one
of
the
things
that's
really
unique
about
gitlab
is
we
have
our
2000
page
handbook
online
and
it
is
created,
stored,
maintained
in
get
lab,
and
it's
also
opens
its
open
comments,
and
so
people
can
contribute
to
it.
So
it's
right
here,
it
says
please
contribute
so
the
details
are
right
there
and
typo
earlier
today.
A
A
B
Thanks
christina
so
today,
I'm
going
to
walk
you
all
through
how
you
can
contribute
to
gitlab
using
our
handbook.
So
if
you're
looking
for
typos,
that's
going
to
be
the
place
to
start,
what
we're
going
to
do
is
we're
actually
going
to
start
looking
directly
at
a
handbook
page
right
now
and
if
you
notice
right
here,
we've
got
this
aue
indication
word:
that's
not
a
real
word.
B
And
that
takes
us
to
the
web
ide.
However,
this
is
not
my
work
get
lab
profile.
This
is
the
type
of
profile
you
all
might
have
when
you're
working
with
git
lab.
This
is
what
you
see
when
you're,
not
a
member
of
a
project
that
you're
trying
to
contribute
to.
You
actually
have
to
fork
the
project,
make
the
changes
and
then
push
those
back
and
merge
those
branches
together.
So
we
can
go
ahead
and
do
that,
we're
going
to
click
go
to
fork
and
it's
going
to
fork
for
us
now.
B
I
already
have
a
fork
installed
the
get
lab.
What
we
call
dashcom
project
is
actually
a
big
project.
There's
a
lot
in
there
and
it's
gonna.
Take
you
a
while
when
you
first
fork
it
it's
gonna,
take
a
long
time.
It's
gonna
say:
project
is
being
forked,
just
wait
and
just
be
patient
it'll,
eventually
pop
up
to
this
screen
right
here.
I
know
this
is
different
from
before,
because
we
don't
have
the
banner
up
top
and
right
here.
I
can
see
that
this
is
the
medicine
around.
B
B
B
So
I'm
going
to
head
to
the
handbook
gitlab
twitch
and
it
should
help
me
find
yeah
twitch
for
evangel.
This
is
where
I
was
so
there's
that
typo
again
we're
going
to
click
open
in
web
id
again
and
it's
a
little
bit
hacky,
but
this
helps
us
find
the
file
tree.
So
we
can
go
sites
handbook
source
handbook.
B
Once
we've
got
those
four
folders
open,
we
need
to
scroll
all
the
way
down
and
see
where
marketing
is
because
marketing
is
the
folder
we
need
to
get
into
and
the
reason
I
know
that
is
because,
when
we're
looking
at
the
file
tree
that
we
originally
saw
marketing
was
where
the
education
program
and
community
relations
was
located.
So
we
need
to
head
to
that
part
of
the
file
tree
so
marketing
community
relations,
education
program,
education,
evangelism,
twitch,
and
there
we
can
see
that
typo
right
there.
B
So,
in
order
to
fix
that
we're
just
going
to
real
quick
change
that
to
education
like
it
should
be,
and
as
soon
as
we
start
typing
in
here,
we
see
the
blue
commit
button
light
up
now.
Remember
we
can't
do
the
work
over
here.
We
had
to
fork
it
first,
so
since
we're
going
to
fork
since
we're
in
our
fork
rather
right
here,
all
we
have
to
do
is
click
the
blue
commit
button.
B
Now
we're
going
to
create
a
new
branch
and
we're
going
to
call
it
I'm
going
to
use
my
name
dash
and
it's
going
to
be
typo
fix
and
we're
going
to
say
twitch
for,
like
the
page
that
we're
doing
it
on
and
we're
going
to
start
a
new
merge
request.
This
is
checked
right
here.
If
that's
not
checked,
there's
another
process
that
I
can
show
you
how
to
do
in
one
second,
but
for.
D
B
Here's
the
merge
request
of
from
see
you
can
see
the
target.
Oh
sorry,
this
is
the
target.
You
can
see
the
source
method
around
gitlab.com
pj
typo
fix
twitch
into
gitlab.com.
This
is
the
master
branch
of
the
gitlab.com
website.
That's
where
the
handbook
lives.
So
we
just
need
to
say
why
it's
happening
and
the
reason
why
it's
happening
well,
rather
the
reason
why
we
say
why
it's
happening
is
because
you
don't
just
want
to
tell
somebody
what
changed
you
want
to
say
why
it
changed
now
for
typos.
It's
very
obvious.
This
is
a
typo.
B
Oh,
that's
a
typo
two!
This
is
a
typo
and
needs
to
be
fixed
for
sure.
That's
obviously
the
reason
we're
fixing
typos
it's
for
readability,
but
if
you're
merging
for
larger
projects
or
if
you're
emerging,
say
into
another
open
source
project
and
you're
changing
some
of
the
code
base
or
you're
adding
a
function,
you
want
to
say
why
it's
being
added,
you
don't
just
want
to
tell
them
what
you're
doing
you
want
to
tell
them.
Why
you're
doing
it?
B
The
y
helps
answer
why
they
should
listen
to
you
and
take
the
merge
request
in
the
first
place,
so
I'm
gonna
go
ahead
and
leave
that
there
it's
just
as
a
typo
needs
to
be
fixed.
This
checklist
is
something
I'm
gonna
show
off
in
another
second
delete
source
branch
for
merge,
request
is
accepted,
squash
commits
leave
those
checked
and
then
I'm
going
to
click
create
merge
request.
B
Now
this
might
take
a
little
bit
of
a
second,
because
this
is
a
large
project
like
I
said
before,
but
once
it's
finished
we're
going
to
see
the
actual
merge
request
itself
right
there
in
front
of
us
okay.
So
once
the
merge
request
goes
through,
this
is
exactly
what
you'll
be
looking
at.
This
is
a
what
we
call
an
mr,
and
this
is
fixing
a
typo
education,
evangelist
twitch
and
I
think
that's
a
pretty
concise,
mr
there's
a
typo
there
in
the
handbook
and
we
fixed
it.
B
So
I
want
you
to
notice
that
some
things
that
automatically
happen-
and
you
might
have
to
refresh
your
page
in
order
to
see
them
because
the
bot
takes
a
little
time
to
do
it.
I've
automatically
been
assigned
to
this,
mr
additionally,
a
label
has
been
added
here
of
community
contribution
that
automatically
it
gets
added
by
get
lab
bot.
So
you
can
see
git
lab
bot
says
thanks
for
your
contribution
after
it
generates
this
message,
it
then
applies
the
label
community
contribution.
B
B
There
are
six
participants
in
this.
You
can
see
I'm
a
participant,
gitlab
bot
is
a
participant,
and
then
these
are
four
people
who
are
team
members
at
gitlab,
lauren
parker
who's,
one
of
our
front-end
engineers.
This
is
john
coughlin,
the
interim
director
of
community
relations.
This
is
christos,
bakarakis
who's,
our
community
contribution
project
lead-
and
this
is
fatima
khalid
who's.
A
developer
evangelist
here
and
these
people
are
all
participants
here,
because
they're
all
capable
of
helping
me
make
this
work.
B
Community
contribution
probably
tagged
some
of
the
community
relations
people
here
and
really,
as
far
as
like
what
you
need
to
do
in
order
to
contribute
to
gitlab.
That's
it
that's
all
you
have
to
do
you
make
this,
mr,
and
then
it's
totally
out
of
your
hands.
This
pipeline
is
running.
It's
checking
a
few
things.
I'm
asking
to
merge
this
into
a
master
for
gitlab
and
like
that's
all
you
have
to
do
so.
Let's
say
you're,
making
a
change
and
it's
something
that
you
don't
automatically
see.
B
B
So
I've
got
a
little
comment
here
that
I'm
going
to
add.
That
is
saying
this
was
updated
on
april
6
2022
just
to
have
a
little
comment
here.
Really,
I'm
just
trying
to
show
you
all
some
changes
being
made.
So
I've
got
this
comment
that
I've
added
I'm
gonna
click
commit.
There's
two
reasons
that
you
wouldn't
have
started
your
merger
quest.
If
you
create
a
new
branch,
it
starts
a
new
merge
request.
B
But
if
you
commit
to
master
which
remember
this
is
the
master
branch
of
your
fork,
not
the
actual
get
my
project,
it
wouldn't
have
an
mr,
but
just
for
fun.
Let's
go
ahead
and
do
new
branch
we'll
go
pj,
we'll
call.
It
comment
twitch
and
let's
go
ahead
and
get
that
bracket
out
of
there,
but
I'm
gonna
unclick
start
an
emergency
quest,
and
I'm
only
doing
this
to
show
you
how
you
would
initiate
a
merge
request.
B
If
you
didn't
automatically
do
one
so
I'm
going
to
commit
that
we're
going
to
let
that
spin
up
all
changes
are
committed.
I've
got
that
new
branch
and
what
I'm
going
to
do
is
I'm
actually
going
to
head
back
to
the
project
itself,
and
this
is
my
fork.
It
says
you
push
pj
comment
twitch.
You
just
did
that
and
I
was
like
good
that's
what
I
wanted
to
do
perfect.
So
what
I'm
going
to
do
is
I'm
going
to
head
here
to
merge
a
question.
You'll
notice.
It
says
zero.
B
There's,
no
merge
requests
here,
right,
new,
merge
request,
sometimes
there's
an
option
up
here.
You
push
pj
comment
twitch
just
now,
would
you
like
to
create
a
merge
request?
I
was
like
heck
yeah.
Let's
do
that,
so
here's
what
it
does.
It
shows
you
exactly
where
you're
coming
from
and
exactly
what
you're
going
into
it's
perfect
that
little
pop-up
there
is
great.
Let's
say
you
don't
have
the
pop-up
for
some
reason
and
you're
going
from
scratch.
New
merge
requests
down
here.
You
will
actually
be
picking
the
target
branch
and
the
source
branch.
B
B
This
is
the
target
project
that
we're
pushing
into.
But
when
you
check
in
here
there's
a
lot
of
projects
in
here
and
they
all
have
someone's
name
and
dashcom.
So
you
want
to
make
sure
you're
doing
the
right
one.
It's
this
one,
it's
usually
at
the
bottom,
then
what
you
do,
there's
that
and
then
you
targeting
master
common
twitch.
What
we're
going
to
do
is
we're
going
to
compare
those
branches,
we're
on
gitlab.com
master,
we're
going
from
source
to
target,
so
we're
going
to
say,
compare,
compare,
branches
and
continue.
B
This
is
a
similar
to
what
we
saw
before
a
merge
request
right.
What
we're
doing
is
we're
going
to
change
that
title.
It's
going
to
be
added
comment
to
twitch
handbook
right.
You
so
same
as
before,
say
why
it's
being
done
making
sure
comments
reflect
recent
changes,
so
people
looking
at
code
can
know
when
new
code
was
added
now.
Obviously,
that's
not
really.
You
can
see
in
like
the
git
commit
like
it's
not
as
big
a
deal,
but
that's
why
I'm
saying
I'm
doing
this
right
now.
You'll
have
better
reasons
other
times.
B
A
D
A
That
you
are
a
student
and
that
also
that
you,
you
are
a
student
and
then
your
university
as
well,
and
that
will
help
when
people
from
get
lab
are
trying
to
help
kind
of
you
know,
mentor
you
and
move
move
your
merge
requests
through.
It
will
help
them
know
that
you're,
a
student
and
you're
just
getting
started,
you're
kind
of
learning
as
well.
So
that's
a
good
thing
to
do
and
then
also,
you
can
add,
a
full
readme
file.
A
D
A
Way
to
kind
of
put
your
not
you're,
really
your
resume,
but
a
readme
is
kind
of
a
file
about
you
and
your
interest
and
your
background
and
kind
of
maybe
your
style.
Like
your
personality,
a
little
bit
of
people
put
fun
things
in
there
like
dogs,
or
you
know
whatever
their
favorite
food
is
pj
likes
korean
food
and
tacos,
so
yeah
tacos
before
you
came
tonight
so
so
stuff
cool
stuff
like.
D
A
A
It
gives
you
kind
of
his
social
profile,
so
we
encourage
all
of
you
to
follow
any
of
our
developer,
evangelists
on
twitter
and
different
social
networks,
because
it's
a
really
great
way
to
kind
of
learn
about
upcoming
opportunities
and
other
other
ways
to
engage
with
the
community,
and
you
can
just
see
he
has
some
of
his
talks
here
that
are
really
cool
blog
posts
and
then
some
insights
as
well,
and
then
one
of
the
really
cool
things
about
that.
I
love
about
get
lab,
especially,
is
that
I.
A
A
The
week
between
christmas
and
new
year's
these
two
weeks,
we
really
encourage
friends
and
family
first
and
time
to
refresh
and
he
did
a
great
job
of
staying
away,
which
is
really
just
as
important.
So
the
point
here
being
that,
as
you
get
more
involved
and
as
you
do
more
projects
on
gitlab
and
you
post
this
out,
there
put
it
on
your
resume
potential.
Employers
and
collaborators
can
come
and
kind
of
see
what
you've
worked
on
and
see
and
it
becomes
a
portfolio
of
a
sense.
A
Kind
of
this
part
of
it,
so
please
sign
up
if
you
haven't
signed
up
and
you
can
also
link
with
your
google
github
twitter
account.
The
one
thing
that
we
do
want
to
mention
is
that
you
get
a
certain
amount
of
free,
ci
cd
minutes
with
a
free
gitlab
account,
but
there
is
a
new
step
that
requires
you
to
verify
who
you
are
and
unfortunately
crypto
mining.
A
A
Unfortunately,
that's
one
of
the
only
ways
right
now
that
there
is
to
do
that,
although
we
are
kind
of
looking
into
other
other
options
so
and
then
once
you're
set
up
there,
you
can
find
an
issue
to
work
on,
so
I'm
gonna,
I'm
also
gonna,
show
you
kind
of
where
to
get
help
so
remember
that
there's
that
getter
channel
as
well.
So
this
is
our
getter
channel
for
getlab
contributors,
and
you
can
see
here's
christos.
A
A
Once
you
have
a
merge
request
or
if
you
need
help,
you
can
reach
out
to
merge,
request,
coaches
and
that's
one
of
the
really
cool
things
about
getlab
is
that
we
have
merge,
request,
coaches
and
there
they
basically
monitor
merge,
requests
and
they're
there
to
help-
and
this
is
the
coaching.
This
is
how
to
learn
how
to
be
a
coach.
But
I
just
wanted
to
show
you
kind
of
the
information
about
it
and
you
can.
You
can
mention
merge,
request,
coaches
by
typing
at
getlab
or
coaches.
A
A
Along
those
are
some
great
great
resources
for
you.
In
our
issue
tracker
we
have
documentation
issues.
So
if
you
go
to
gitlab.org
and
then
get
lab
and
issues,
you
can
build
a
search
that
says,
label
equals
good
for
new
contributors.
So
that's
that's
an
excellent
way
to
find
out
if
the
community
is
kind
of
you
know
welcoming
for
people
who
are
new
and
then
that
you
can
also
search
for
issues,
accepting
merge,
requests
and
then
documentation.
A
A
Oh
here
we
go
there.
I
knew
I
had
a
link
somewhere.
I
wanted
to
actually
show
you
what
that
board
looked
like
so
again
and
I'll
put
it
here
in
the
chat,
although
you
can't
also
get
it
from
that
workshop,
so
again,
label
good
for
new
contributors,
accepting
work
deposit
documentation
and
you
can
sort
this
by.
Is
it
high
priority?
What's
the
create
a
date
updated
day
due
date,
etc?
A
And
then,
let's
just
take
a
look
at
the
first
one
that
popped
up
clarify
what
the
name
space
will
be
when
you
source
your
module.
So
let's
open
that
in
a
new
tab
and
see
that
okay,
this
was
open
two
months
ago
by
mason
and
it's
explaining
kind
of
you
know.
It
looks
like
this
person
is
asking
us
to
to
give
some
more
detail
around
the
terraform
module
registry
and
we
can
see
the
labels
that
are
here
so
good
for
new
contributors,
documentation,
accepting
merge,
requests,
it's
also
giving
some
product
labels
so.
A
It
is
a
major
focus
of
our
ceo
and
our
company
to
get
contributors
and
encourage
them
to
come
and
welcome
them
to
build
the
you
know,
build
up
the
product,
so
it's
better
for
everyone
right
and
so
don't
you
know,
don't
don't
worry
about
being
shy,
or
you
know
embarrassed
that
this
is
especially
for
students.
You
you
have
that
that
tendency-
and
I
know-
because
I
I
was
a
professor
in
pj-
was
also
a
teacher
and
english
teacher
for
many
years
as
well.
A
So
we
had,
we
got
that
and
this
is
the
reason
we're
showing
you.
This
is
that
you
know
these
people
are
here
to
help
at
the
end
of
the
day.
So
that's
that's!
That's
why
we're
here
so-
and
here
is
susan-
south
horn
she's,
our
technical
staff
writer.
So
she
is
in
here
working
on
this
and
and
kind
of
already
kind
of
helping
right,
the
person
who's
doing
the
contributing
and
when
you,
if
you
were
to
go
to
documentation
and
find
an
issue,
you
want
to
make
sure
that
you
look
and
see.
A
Okay,
clearly
someone's
already
working
on
this.
So
if
you
you
know,
you
don't
want
to
try
to
start
from
the
beginning.
You
either
want
to
help
where
they're
at
or
find
a
new
one,
where
it's
clear
that
someone
hasn't
already
kind
of
started
working
on
it,
and
so
let
me
go
back
to
the
issue
board
here.
A
Help
as
well,
you
can
tag
either.
One
of
us
and
pj
will
put
our
get
lab
handles
in
the
in
the
chat
so
that
we
can
keep
an
eye
on
that
as
well.
But
I'm
going
to
show
you
one
of
our
team
members
here,
greg
who's,
awesome,
greg,
myers,
very
a
huge
advocate
for
open
source.
He
we
told
him
we
were
doing
this
workshop
and
he
used
the
linter
and
created
this
snippet
of
all
of
these
typos,
and
so
this
is
a
list
of
typos
and
it
shows
you.
A
A
Sites
handbook
source
about
source
index
html
and
you
find
line
122
and
you're
gonna
find
that
this
word
is
spelled
wrong,
and
so
then
you
can
fix
it
and
make
it
commit
and
then
the
commit
will
you
can
open
a
merge
request
or
you
can
keep
keep
committing
if
you
on
that
branch
right
and
then
it'll
go
to
the
to
the
team
to
review.
So
I
need
to
we
need
to
add.
A
A
To
mention,
if
you
decide
to
do
this,
you
can
just
do
one
and
that's
totally
fine.
We
will
love
to
just
take
one
typo
and
move
with
it,
but
let's
just
say
that
you
see,
for
example,
here
that
you
know
here's
one
from
support
across
espeldrun
and
then
here's
one
from
data
team
and
you'll
see
that
further
is
missing
the
r
okay.
A
So
in
the
value
of
iteration
in
git
lab
we
basically
we
we
follow
this
idea
that
you
want
to
make
you
know
the
smallest
changes
kind
of
possible
and
not
try
to
lump
a
bunch
of
changes
together.
So
don't
feel
like
you
have
to
go
through
this
first
of
all
and
fix
everything.
Obviously,
there's
a
there's,
a
bunch
of
tables,
but
what's
more
important,
is
that
you
see
how
this
is
organized.
A
Where
this
is
all
data
team
typos,
you
don't
want
to
include
changes
from
the
data
team,
along
with
changes
from
professional
services
and
one
merge
request,
because
they're
different
code
owners
and
different
teams-
and
so
if
you
want
to
make
a
couple
different
commits
just
to
kind
of
get
the
practice.
Then
we
just
recommend
you
stay
kind
of
within
the
team
and
you'll
be
able
to
see
that
here
right
because
it
says
data
team
and
then
this
one
says
customer
success
as
a
division.
And
then
professional
services
is
division.
A
And
so,
if
we
do
have
a
large
group,
then
we
recommend
here
that
you
write
c
huby
imt
I'll,
take
you
know
line,
say
I'm
going
to
fix
this
one
I'll
take
line
25.,
and
so
that
way
and
we're
working
through
the
demo.
The
workshop
today,
if
you're
going
to
take
one
go
ahead
and
put
that
down
there
so
that
one
of
your
other
student
colleagues
doesn't
come
and
grab
it.
So
that
gives
you
that
idea
and
then
pj
gave
you.
A
Yes,
you
can
fix
several
type
typos
in
a
single
merge
request
and
then
before
we,
you
know,
stop
the
kind
of
formal
part
of
our
presentation.
I
did
want
to
share
oops
darn
it
pj.
I
didn't
update
this.
The
next
hackathon
is
in
may
so
maybe
pj
can
help
me
grab
those
dates,
real
quick,
but
we
have
a
hackathon
every
quarter,
which
is
basically
there's
four
a
year
and
the
next
one
is
coming
up
at
the
beginning
of
may
and
really
what
we
do
is
we?
Oh.
A
You
know
what
I
have
the
landing
page
right
here,
so
I
can
there
we
go
in
a
second.
I
knew
it
was
right
at
the
beginning,
and
this
kind
of
shows
you
everything
that
you
need
to
know
about
joining
the
hackathon
and
during
the
session.
It
shows
you
how
to
join
the
sessions,
how
to
get
help
all
of
the
different
issues,
and
you
can
see
last
time
we
had
188,
merge
requests
submitted
so
and
there's
really
cool
prizes,
a
t-shirt,
coffee,
canister
charger.
A
And
then,
if
you
are
the
grand
prize
winner,
where
you
get
the
most
points
for
the
hackathon,
then
you
get
a
really
special
swag
kit
and
all
of
these
things
kind
of
can
add
up
to
different
experiences
and
you
know
building
your
portfolio,
but
then
also
every
time
you
know
you
make
a
commit.
You
kind
of
can
be
on
the
road
to
get
that
hero
as
well.
So,
okay,
that's
another
kind
of
cool
cool
cool
aspect
of
it.
A
So
I
think
that
is
our
last
yeah
last
slide
for
today
and
I
wanted
to
share
as
well
that
you
are
welcome
to
connect
with
pj
and
I
on
linkedin
and
twitter
and
pj
often
twitter
posts
on
twitter,
while
he's
switching
on
on
twitch.
He
hosts
shows
and
does
some
demo
he's
learning
python
right
now
so
he's
returning
while
he's
doing
that,
which
is
a
cool
way,
you
can
join
in
and
participate.
A
C
Thank
you
guys
for
the
super
detailed
instruction.
I've
never
seen
open
source
contribution
that
easy.
To
be
honest,
I
do
have
a
quick
question.
So
earlier
you
mentioned
there's
a
engineer
from
gitlab
called
his
name
is
nick
and
he
helped
label
the
issue.
So
is
it
like
a
manual
process
or
is
there
any
like?
I
don't
know
machine
learning
involved
to
help
label
or
can
you
I'm.
B
B
Template
template
is
the
word
I
I
forget
more
often
than
any
other
word.
There
are
issue
templates
that
are
suggestions.
You
actually
saw
an
issue
template
in
the
merge
request.
I
was
doing
so
when
I
made
a
merge
request.
It
automatically
populated
the
field
with
a
bunch
of
instructions
at
the
bottom
of
that
merge
request,
and
let
me
find
that
again
real
quick
that
merge
request.
B
I
did
not
pick
a
label
for
it.
I
just
went
through
and
clicked
merge
request,
and
you
can
see
that
because
it
was
a
community
contribution,
a
label
was
automatically
applied
because
the
issue
template
had
a
quick
action
to
attach
a
label
to
it.
So,
for
instance,
christina
was
talking
about
on
my
twitching
earlier
when
I
do
a
twitch
show
where
I'm
interviewing
gitlab
team
members,
I
have
them,
fill
out
an
issue
template
and
at
the
bottom
of
that
issue
template
it
has
a
quick
action
to
tag
it
with.
B
A
You
know
certain
labels
here
as
well,
so
I
don't
know
if
we
would.
I
don't
know
how
it's
you
know
doing
that.
Maybe
it's
based
on
certain
language
but
like
pj
mentioned
the
other
one.
It
applied
the
community
contribution
bot
because
I
knew
it
was
someone
who
doesn't
work
at
get
lab
who
forked
the
handbook
and
then
tried
to
make
it.
You
know
a
merge
request,
so
it
labeled
it
automatically
with
a
community
contribution.
C
And
see,
and
then
also
I
was
looking
at
the
list
of
the
open
projects,
the
yeah,
the
open
source
projects
that
we
can
contribute
to,
and
I
know
do
you
have
any
like
suggestions
on
how
to
choose
a
project
because,
let's
say
somebody
who's
new
to
contribution
right.
It's
really
hard
to
choose
like
which
project
I
am
capable
of
contributing
to
which
one
is
easier,
and
things
like
that.
A
A
Let's
just
get
yeah
and
here's
the
security
one,
and
this
this
talks
about
some
of
the
policies,
the
contribution
flow,
oh
darn
it
I
was
specifically
looking
for
the
text
stack.
Maybe
while
I'm
talking
pj
can
I
know,
there's
a
list.
We
had
a
really
good
list
in
one
example
where
it
said
you
need
ruby
on
rails.
You
need
go,
you
need
this,
you
need
this.
A
I
think
it
was
in
the
in
the
actual
development
one,
but
I
would
say
starting
there,
I
think,
is
a
really
good
place,
so
look
and
make
sure
that
you
you
have
some
of
those
and
I
think
for
a
lot
of
starting.
You
know,
starting
out
developers,
front
end
where
they
maybe
already
know
like
vue.js
or
java,
or
something
that's
a
little
bit
more,
like
they've
done
front-end
projects
and
then
there's
some
front-end
ux
things
that
are
simpler
to
fix.
A
I
would
say,
for
the
most
part,
any
project
is
going
to
have
some
kind
of
front-end
development
and
the
tools
there
are
going
to
tend
to
be
a
little
bit
more
accessible.
So
if
I
had
to
summarize,
I
would
say,
look
at
the
tech
stack,
consider
front
end
and
then
see
if
they're
welcoming
the
new
code
contributors
and
we.
C
A
A
A
B
There's
that
expectation
you
have
to
be
at
a
certain
level,
it's
okay
to
be
not
quite
there
yet
and
for
the
merge
request
or
the
pull
request
or
whatever
it
is
that
you're
doing
to
contribute
for
your
contribution
to
be
a
bit
of
a
stretch
for
you
and
something
you
have
to
work
at.
That's
fine.
A
lot
of
people
contributing
to
open
source
will
be
like.
B
Oh,
I
can't
do
that
yet
I'll,
wait
until
I'm
better
use
open
source
to
get
better
and
if
you're,
looking
at
a
project
and
it's
ruby
on
rails
and
you've
never
touched
ruby
on
rails.
Don't
go
to
that
one!
If
you
go
to
one,
that's
go
and
you've
done
a
little
bit
ago.
Take
a
look
and
see
if
it's
something
you
think
you
could
do
at
the
very
least.
Don't
don't
count
yourself
out
immediately
like
if
I
see
ruby
on
rails.
B
I
know
to
turn
around
and
go
to
go
the
other
way,
because
that's
not
for
me,
but
christina,
is
absolutely
right
that
using
the
issue,
search
bar
is
really
good
and
it's
not
like
a
normal
search
bar.
Our
search
bar
is
kind
of
cool
where
you,
when
you
click
into
it's
like
okay.
What
are
you
looking
for
issue
label?
Epic
and
you
pick
that
and
then
you
pick
either
the
equal
sign
or
exclamation
equals.
So
when
I
said
oh,
you
can
do
not
back
end
christina,
just
went
with
oh
I'll.
B
Just
do
looking
for
front
end.
Only
so
tons
of
ways
you
can
look
for
is
not
and
those
fruits
are
actually
low
hanging
fruit.
Labels
too.
I
learned
that
the
other
day
so
you're,
like
hey.
None
of
this,
has
a
back-end
label
once
I
finish
this
search,
so
it's
not
a
it's
not
like
a
regular
search
bar
you
might
be
used
to,
but
I
really
like
our
search
bar
and
the
way
it
works,
but
yeah,
absolutely
you
can
look
for
the
most
recent
one.
B
A
A
Wait
is
going
to
be
easier,
so
that's
a
great
point
dj.
You
can
sort
it
ascending,
so
these
are
going
to
be
ones
that
are
easier,
so
here's
an
example
of
update
the
debian
documentation.
I
just
looked
at
this
one
the
other
day,
so
there's
a
couple
things
that
are
missing
from
the
the
documentation
on
how
you
work
with
debian,
and
so
here's
a
really
you
know
good
example
of
they
fixed
a
few
of
them.
A
But
there's
a
few
left
and
so
documentation
again
is
a
great
way
to
get
started
because
you
can
go
play
around
with
debbie
and
play
around
with
where
it's
at
follow
the
documentation
and
then,
as
you're
learning,
make
the
contribution
make
it
better,
but
to
pj's
points
back
to
the
issue
board
here.
Priority,
I
think,
was
what
was
what
pj
was
talking
about
so
priority.
If
you
want
to
work
on
something,
that's
you
know.
A
You
know
in
terms
of
is
an
urgent
and
that
you
know
to
get
started
or
you
can
sort
it
the
other
way
and
say
I
want
to
work
on
something.
That's
you
know
really
really
important.
I
don't
know.
Sometimes
it
doesn't.
Obviously
this
has
been
a
year
ago,
but
you
get
the
general
you
know
idea.
So
there's
that
weight
that
shows
kind
of
how
long
it's
going
to
take
and.
C
C
B
We
heard
from
the
community
that
it
might
be
nice
to
be
able
to
search
by
language
used
for
people
who
are
contributing,
but
it
is
way
more
powerful.
It
actually
comes
from
the
community.
Otherwise
I'm
just
like
running
messages
back
and
forth,
but
if
you
put
it
in
there
and
it's
it's
more
important
because
it
came
directly
from
you,
you
took
the
time
and
the
effort
and
the
work
to.
Let
us
know
something,
and
so
we
tend
to
take
those
seriously.