►
From YouTube: Reviewing an MR in GitPod that requires editing .yml
Description
Alexis does a design review on a Service Desk MR
A
Hey
there
alexis
here
designer
on
plan,
so
I'm
going
to
attempt
to
quickly
walk
you
all
through
reviewing
this.
Mr,
I
haven't
reviewed
an
mr
exactly
like
this
and
sometime.
I
think
I
actually
recorded
myself
walking
through
that.
Mr,
so,
let's
see
what
I
remember
of
adding
a
bunch
of
yaml
files
in
gtk,
so
this
is
regarding
service
desk.
A
So
we'll
see
so
you
know
I
look
at
this
for
contacts,
which
is
the
originating
issue
of
the
mr
and
again
not
totally
well
versed
in
this.
So
I
had
to
take
a
second
to
look
at
it,
but
again
around
service
desk
around
how
to
enable
service
desk.
Basically-
and
you
know
how
that
involves-
custom
emails,
there's
something
called
the
incoming
email
which
is
actually
in
it
enables
service
desk
versus
the
service
desk,
email
which
you
might
expect
enables
service
desk.
A
That
doesn't
so
there's
some
stuff,
and
I
think
we
can
keep
improving
this.
But
for
now
we
are
tinkering
around
with
some
of
the
fields
disabling,
enabling
and
giving
better
guidance
to
make
a
little
bit
of
make
some
of
this
more
clear.
So
let's
jump
in
and
stop
talking
about
it,
but
I
do
appreciate
all
the
work.
That's
been
done
here
and
all
the
guidance
on
this.
Mr,
so
let's
dig
into
it.
I
have
gdk
open.
A
A
And
I
probably
typed
that's
wrong,
so
we'll
see
yeah.
I
did
type
that
wrong
okay,
so
I
don't
know
if
this
I
don't
know
if
this
is
going
to
change
at
some
point,
but
I
always
have
to
do
this.
This
is
normal,
or
at
least
I've
always
done
this.
I've
always
had
to
reset
the
password
every
for
every
new
instance.
I
use.
A
A
All
right
so
service
desk,
we
haven't,
enabled
it
so
we'll
see
something
like
this
and
again
like
I
said
I
think,
there's
quite
a
few
things
we
can
improve
here.
Obviously,
but
we
have
the
stock
and,
like
I
said
before,
there's
like
this
incoming
email
right,
that's
how
you
enable
it
and
that's
part
of
the
confusion
there.
So
let's
first
enable
service
desk-
and
we
have
information
about
how
to
do
this
here.
A
A
A
All
right,
so
yes,
that's
false.
We
want
it
to
be
true
and
I
believe
that's
correct.
I'm
going
to
save.
I
think
I
saved
so
I'm
a
little
less
clear
on
what
to
do
here
in
get
pod,
because
if
you
want
to
restart
I'm
just
kind
of
refreshed
and
just
hopefully
it
does
what
I
wanted
to
do,
I
don't
think
it
will.
Let's
see.
A
A
I
just
went
to
the
other
tab,
basically
to
start
and
I'm
gonna,
let
it
restart
it'll.
Take
a
second
and
I'll,
see
you
in
a
second
okay.
I
left
this
go
for
a
second.
Let's
see
if
get
pot
or
gdk
is
back
again
nope.
It
is
not
so
we'll
wait.
A
little
longer
give
me
a
second
okay.
I'm
gonna
try
again
by
opening
up,
let's
kind
of
start
over
nope.
A
Okay,
well,
your
pot
house
decided
that
hates
me.
You
will
have
to
try
something
else
to
be
continued,
hey
alexis.
Here
again,
I
am
back
so
what
I
did.
I
just
set
up
a
new
instance
and
her
workspace.
I
guess,
and
went
through
and
enabled
everything
before
opening
git
pod
or
like
before
opening
this
local.
So
I
could
chuck
it
out
we'll
see
if
that
works.
A
Yep,
okay,
but
I've
noticed
this
sometimes
in
get
pod
where,
if
you
like,
if
I
should,
I
think
what
was
the
problem.
There
were
some
things
I
did
and
it
kind
of
just
stumped
the
entire
process.
It
wasn't
when
I
added
a
license,
it
might
have
been
when
I
made
changes
before
adding
a
license.
I
don't
know
sometimes
it's
really
finicky
and
just
wants
me
to
like
make
the
changes
before
checking
out
the
changes
before
checking
out
the
branch.
I
guess
I
should
say
so:
let's
go
through
this
again.
A
A
A
A
Hold
on
just
one
night,
I
know
you
all
really
want
to
watch
us
so
just
in
general
now
I'm
saying
if
I
can't
even
open
the
service
desk
accordion-
and
I
don't
know
why
so
I
don't
know
I
might
want
to
go
back
and
disable
the
the
one
that's
not
enabling
like
just
enabling
service
desk
and
see
if,
like
just
enabling
service
desk
works,
but
like
not
going
any
further
and
see
how
that
impacts
things
all
right.
Well,
I
guess
we'll
try
doing
that.
Just
a
minute!
A
A
Oh,
it's
right
here,
okay,
so
I
stopped
the
workspace
and
then
I
basically
just
went
back
to
it
and
logged
in
again-
and
I
didn't
show
this
of
course,
because
I
actually
wasn't
expecting
it
to
work,
but
it
did
work
so
I
logged
in
again,
then
I
went
back
to
service
desk.
I
expanded
this
and
I
can
see
I
can
see
this
now.
So
there
is
something
interesting
going
on
where
I
don't
believe
this
is,
I
think,
yeah.
This
is
what
we
have
live
at
the
moment.
So
that's
a
little
confusing,
not
expected.
A
A
A
A
So
I
need
to
go
through
and
disable
this
now.
I
had
enabled
it
because
I
just
wanted
to
see
if
I
could
even
like
review
this
properly
in
github.
So
now
I
need
to
go
through
and
set
this
to
false
right,
and
what
I
would
expect
to
happen
now
is
to
have
something
like
this,
where
it's
disabled
and
it
basically
tells
me
to
go
through
and
edit
the
ammo
file
and
set
this
to
true.
But
I've
already
done
that.
A
A
This
email
was
false
so
that
I
could
test
out
this.
Other
flow
basically,
so
I
did
that
then
I
stopped
the
workspace
and
I
started
this
workspace
back
up
and
I
was
able
to
go
into
a
project,
go
to
general
settings
and
look
at
service
desk,
and
now
I
see
something
a
little
different.
This
is
expected.
A
A
A
But
having
it
like,
as
part
of
this
sentence,
feels
different
than
kind
of
the
standards
we
have
in
place
up
here,
so
I'll
look
at
pajamas
and
kind
of
see.
What's
intended
for
these
states,
and
in
general
I
mean
this
needs
to
be
worked
on
like
there's
stuff,
we
could
do
better
here
just
to
make
it
a
little
bit
more
clear.
I
mean
if,
if
I
can't
edit
this
right,
I'm
not
sure.
For
example,
I
mean:
do
we
even
need
to
show
this.
A
I
mean,
I
think
we
need
to
show
something
right
like
to
say
we
need
to
do
this
within
the
email
file,
I'm
just
trying
to
think
about
like
what
is
the
best
kind
of
like
empty
state
for
this,
because
users
have
to
go
to
another
location,
that's
outside
of
get
lab
in
something
to
configure.
So
I
don't
know
this
is
something
to
think
about
for
nbc.
A
I
might
might
just
say
that
this
is
better
than
it
was
because
it's
a
lot
less
misleading,
and
then
we
can
keep
thinking
about
how
to
improve
this
and
what
is
a
better
empty
state
here?
How
might
we
best?
I
mean?
How
do
we
better
guide
users
in
editing
their
yamo
and
then
in
the
future
like
do
they
have
to
edit
ammo?
Is
there
something
we
can
do,
especially
for
self-manage?
A
I
don't
know
so
something
to
play
around
with
there,
but
the
main
thing
I
wanted
to
show
y'all
was
being
able
to
get
to
this
in
the
first
place,
which
we
finally
were
able
to.
We
just
had
to
start
and
stop
the
get
lab
work
space
a
bunch
of
times
or
they
get
get
pods
yeah
I've
been
looking
at
this
tool
and
get
pod
workspace,
but
so
from
here
I
checked
out
these
two,
these
two
kind
of
like
flows
where
it's
disabled
right.
A
So
this
means
I
have
service
desk
enabled,
but
I
don't
have
these
custom
names
enabled
and
then
here
I
do
have
both
service
desk
in
the
custom
name
enabled
so
I'll.
Take
a
look
at
this
I
think,
like
I
said,
I
wasn't
really
involved
in
this
the
ux
of
this
and
again
that
makes
the
context
a
tiny
bit
difficult,
but.
A
And
it
does
make
it
slightly
less
confusing,
so
we
don't
just
totally
hide
it
anymore.
They
they
understand
that
they
can
do
this
so,
for
example,
the
scenario
of
let's
say
as
a
user.
I
set
up
service
desk
right
with
my
incoming
email,
but
I
see
that
there's
this
or
like.
I
want
to
set
up
this
this
custom
that
configure.
A
I
want
to
configure
the
custom
name,
but
I
don't
see
anything
about
how
to
do
this
right
because
it's
not
in
the
ui
like
I
don't
even
maybe
know
it's
an
option
so
now
at
least
we
have
this
available
user
knows
they
can
do
this.
They
can
see
the
documentation
but,
like
I
said
this
wasn't
here
before
so
I
think
I'm
going
to
think
around
this,
but
I
think.
A
A
A
A
Cool,
so
what
I'm
going
to
do
is
again
this
kind
of
takes
up
more
time
because,
like
I
said,
I
haven't
really
looked
at
the
ux,
so
what
I
will
have
to
do
here
is
kind
of
quickly
mock
up
something,
not
mock
it
up
like
it's
not
going
to
look
great
just
like
give
some
direction
on.
Actually,
let's
not
do
this
input
here.
A
Let's
revise
the
the
copy
really
fast
it'll
solve
the
problem
in
a
similar
way
to
allow
the
user
to
understand
that
there's
action
they
can
take
here
that
they
have
the
option
of
adding
project
name,
but
without
this
kind
of
confusing
blank
input
or
if
we
keep
the
input,
it
probably
should
have
something
in
it.
I
just
I
don't
really
know
the
value
of
seeing
that
so
yeah.
A
So
I
would
comment
back
that
information
or
if
this
is
something
we
need
like
asap,
it
is
better,
it
is
an
improvement,
so
we
could
do
this.
I
could
just
say
yes,
okay,
I
will
approve
this
just
make.
The
small
changes
like
you
know,
make
this
blue
blue
500,
or
instead
of
400
or
whatever
it
is,
and
maybe
update
the
copy
really
fast
just
so
it
sounds
a
little
friendlier
stuff
like
that,
and
then
I
would
create
a
ux
stat
issue
to
follow
up
on
things
like
hey.
A
I
don't
know
that
we
really
need
a
disabled
box
there,
things
like
that
and
then
like
further.
We
would
think
about
like
what
is
the
empty
states
in
service
desk.
Maybe
and
like
those
other
things
I
mentioned
before,
like
how
do
we
make?
How
do
we
improve
this
flow
in
general?
Right,
like
you
know
these
ammo
files,
how
do
we
support
less
advanced
users
here?
A
So
that
is
what
I
would
think
here,
I'm
just
looking
at
different
stuff.
Just
looking
at
this
save
changes
button,
it's
it
seems
like
it's
floating
around
anyway
yeah,
so
I
would
leave
comments.
I
would
tag
the
requester
back
and
then
once
the
changes
were
made,
I
would
go
ahead
and
print
a
purpose
and
it
would
get
reviewed
by
other
people
or
get
merged
in
hopefully,
so
that
is
scratching
the
surface.
On
this
semi
review.
I
hope
this
was
helpful
and
I
will
talk
to
you
all
later.
Bye.