►
From YouTube: Faster Contributing with GitPod
Description
In this video I dive in to how you vcan contribute to GitLab without having to run a single line of set-up code. Run the GDK in the cloud with the power of GitPod!
A
You
know
you
take
something
like
this
or
button
button
success
and
replace
it
with
button
geo
button
button
success
and
it's
pretty
easy.
You
can
do
a
regex.
In
fact,
I
tried
doing
that
myself
as
well,
but
the
problem
is
when
you
want
to
see
these
buttons
to
verify
that
the
changes
you've
made
actually
work.
A
You
need
to
then
download
and
install
the
gdk,
which
is
a
pretty
big
project
and
it's
great
when
it
works.
But
let's
be
real.
It's
it's
not
the
easiest
thing
to
set
up
it's
fantastic,
but
for
changing
a
button.
It's
a
lot
of
work
right.
A
So
I've
come
across
gitpod
right,
which
is
absolutely
fantastic
and
basically
gets
around
us
having
to
set
up
the
whole
gdk
thing,
so
it
it
gives
you
not
only
like
a
vs
code
style,
editing
experience.
A
It
also
combines
the
actual
dev
environment
as
well,
and
we've
set
it
up
at
gitlab
so
that
it
uses
the
gdk
for
this.
So
it's
running
the
gdk.
In
the
background
on
a
I
don't
know,
I'm
going
to
say
the
cloud.
Why
not?
I
don't
fully
know
how
it
works,
it's
pretty
magic,
but
it
does
work
and
it's
really
easy
itself
as
well,
so
you
can
just
log
in
with
your
gitlab
account,
so
obviously
I've
already
created
an
account
and
we
just
create
a
new
workspace.
A
I've
forgotten
how
to
do
it
already.
Okay,
put
your
browser
to
a
gitlab,
github
or
bitbucket
repository
eg,
this
one
okay,
either
prefix
the
url,
the
address
bar
I'll
click,
the
gitpod
button.
If
you've
installed
the
github
browser
extension,
so
you
can
install
the
browser
extension.
I've
not
actually
done
that.
I'm
going
to
go
over
to
this
one
oops.
A
Right,
okay,
so
I
won
this
is
this
is
the
button
I
want
to
actually
change.
So
if
I
go
to
the
project
overview,
so
obviously
I
have
developer
access
to
gitlab,
but
you
probably
want
to
use
your
fork
if
you're
using
a
fork
and
what
does
it
say.
A
Right,
okay,
so
that
this
this
takes
a
while,
obviously
we're
setting
up
the
whole
gdk
and
and
whatever
it
is
so
get
to
this
point
in
the
screen
and
go
make
a
cup
of
tea
or
cup
of
coffee
or
whatever
it
is.
You
want
to
drink,
okay,
so
when
that
finally
loads,
you
get
this,
which
is
an
editor
on
the
left
side
of
the
screen
and
in
this
preview
on
the
on
the
right
side
of
the
screen.
A
Let's
allow
that
pop-up
and
then
this
this
is
this-
is
your
local
version
of
gitlab
right
local
to
this,
this
dev
environment?
So
it's
running
in
the
cloud
any
changes
you
make
to
the
github.
I
think
it
lab
source
code
over
here
gets
gets
made
in
this
instance
of
gitlab,
which
is
really
good.
A
You
can
sign
into
that
instance
with
root
and
the
password
is
five
life
like
that.
It's
in
the
gdk
documentation,
I'll
put
it
in
the
description
this
video
too.
So
we
don't
want
to
save
that
password,
but
we
do
want
to
log
in
now.
The
only
thing
is
this
is
actually
the
community
version
of
github.
It's
not
the
full
enterprise
edition.
A
So
when
you're
picking
these
up,
if
you
look
this
this
issue
that
I've
picked
up
here,
it's
in
the
ee
directory,
so
without
a
license,
we
can't
actually
see
you
know
the
the
thing
that
we're
changing
here,
because
we
need
an
ultimate
license
to
even
see
this
feature.
A
So
what
you
can
do,
if
you
don't
have
a
license,
is
when
you're
looking
for
these
just
make
sure
it's
not
one
like
this,
where
it's
ee
app
views
and
it's
just
the
ones
that
are
in
app
views.
So
there's
a
few
of
them.
App
views,
app
views,
app
views,
deploy,
keys,
see
there's
a
few,
but
just
avoid
the
ee
once
if
you
don't
have
a
gitlab
license
that
allows
you
to
see
our
enterprise
features.
A
A
So
what
is
that
click
on
a
project,
and
then
it
was
settings
and
default
there.
We
had
default
issue
template,
so
I'm
guessing
is
this
save
changes
button
here,
but
let's
shrink
this
down
a
little
and
let's
find
btn.
A
Oh
there's,
two
buttons.
Oh
I
see
okay,
so
the
collapse
in
expand
is
also
part
of
this.
So
we
need
to
update
this
one
as
well
and
this
one
down
here,
so
we
should.
In
fact
I
think
this
is
exactly
like
the
example
in
the
epic,
so
yeah
replace
button
button
success
with
button
gl
button
button
success,
so
we
just
need
to
replace
this
with
gl
button
and
we'll
do
this
one
up
here
as
well,
so
gl
button
and
then
the
easy
way
to
check.
A
If
we
hover
over
this,
you
see
this
there's
not
really
a
big
border
same
with
this
collapse
button.
So
if
we
get
a
screenshot
hovering
over
this.
A
They'll
come
in
handy
later
and
then
we
where's
my
sidebar
there's
my
sidebar
reload
this
page,
it's
better
to
click
on
the
page,
then
actually
reload
it
at
the
top
here,
because
for
some
reason
this
takes
you
right
back
to
the
root,
I'm
not
sure
why
that
is.
A
A
Okay
and
let
me
scroll
down,
where
are
we
where's
it
going
default
issue
template
there
we
go
so
you
see
you've
got
that
nice
thick
border
on
on
this
button
now.
So
it's
a
to
propagate
that
button
same
with
save
changes,
so
we
can
screenshot
that
too.
A
So
now
we
have
the
two
screenshots
that
we
want
for
our
parallel
merge
request
layer.
We
just
need
to
create
that
merge
request
right.
So
this
is
done.
Let's
just
make
sure
the
buttons
still
work.
I
don't
see
why
they
wouldn't
I'm
not
gonna,
bother
clicking
that
it
works.
It's
a
button
right,
okay,
so
we
can
go
over
here
and
you
can
use
the
source
control
stuff.
A
I'm
not
gonna
do
that,
because
I
don't
normally-
and
I
have
no
idea
what
I'm
doing
with
it.
So
I'm
going
to
open
a
new
terminal
window
here.
A
A
Let's
get
the
issue
number
update.
A
A
Damn
it
don't
don't
use
shortcuts
to
close
the
the
window,
because
you
end
up
closing
the
browser
window,
which
closes
everything
so
better
in
mind.
All
right,
that's
gl,
button
classes
to
was
it
issue.
A
Issue:
settings:
okay,
save
that
and
then
click
the
cross.
Don't
use
the
shortcut
and
let's
see
if
this
works
get
push
yeah
we
need
to
set
the
upstream
origin.
This
is
just
standard
good
stuff.
Again,
if
you
prefer
using
the
the
built-in
thing
that
you
get
with
vs
code,
use
that
I
don't
really
use
it
normally,
so
I'm
not
fully
sure
what
I'm
doing
there,
so
I'm
just
using
the
normal
terminal
stuff,
but
that
should
push
it
up
and
give
you
a
new
merge
request.
A
Right
here
so
in
here,
I'm
going
to
do
this.
A
Template
settings
screenshots
strongly
suggested,
so
what
I
like
to
do
is
screenshots
create
a
cheeky
table.
A
A
A
A
There's
no
tests
or
there
might
be
we'll
find
out,
but
I
think
we're
fine
tested
in
all
supported
browsers.
I
haven't
actually
done
that,
so
I'm
going
to
leave
that
blank
and
do
that
afterwards.
No
one
wants
to
watch
me.
Do
that
informed
infrastructure
department.
In
fact,
let
me
set
that
to
do
a
draft.
A
There's
no
reason
for
infrastructure
security
is
fine.
Let's
just
delete
that
section
related
to
this
issue.
That's
good
right
now,
in
theory,
I'll
sign
it
to
myself
now
submit
that
mod
request
and
now
again
this
floor
might
be
different
for
yourself
mine's
a
little
simpler
because
I'm
a
developer,
a
git
lab
and
I
have
access
to
the
project
and
everything,
but
you
may
not.
A
A
So
if
you
click
on
change
log
entry,
it
tells
you
how
to
add
them
in
you
can
do
them
yourself
manually
or
you
can
do
the
the
easier
version
which
was
just
in
the
the
terminal
inside
here
we
can
do
bin
slash
change.
Log
dash
m
for
merge,
request
and
then
come
over
here
and
go
merge.
Request
number
oh
paste,
that
in
there
and
then
a
little
message.
A
A
This
I
don't
know
why
I
did
that
I've
never
seen
you
do
that
before
yeah,
just
close
it
when
you're
done,
I
guess
and
then,
if
we
go
to
get
status,
see
we've
got
our
change
log
in
there
now,
so
we
can
do
git,
add
dot
and
then
hit
commit.
A
A
In
the
cloud
right,
let's
say
so,
we
should,
if
we
refresh
this,
see
that
we've
got
two
commits
now
and
we
can
check
off
change
log
entry,
and
this
is
this-
is
ready
to
be
to
be
submitted.
If
you
don't
know
who
to
submit
it
to
just
tag
me
in
here.