►
From YouTube: GitLab 13.4 Kickoff - Create:Editor
Description
Editor 13.4 Planning Issue - https://gitlab.com/gitlab-org/create-stage/-/issues/12705
Web IDE Category Direction - https://about.gitlab.com/direction/create/web_ide/
- Bug in `.gitlab-ci.yml` feedback: https://gitlab.com/gitlab-org/gitlab/-/issues/232761
- Snippets with multiple files: https://gitlab.com/groups/gitlab-org/-/epics/2829
- Use Monaco for all editing: https://gitlab.com/groups/gitlab-org/-/epics/498
- Implement Web IDE button in diff tab of MR: https://gitlab.com/gitlab-org/gitlab/-/issues/21654
A
Hi,
my
name
is
kai
armstrong,
I'm
the
product
manager
for
the
editor
group
of
the
create
stage
here
at
git
lab
and
I'm
here
to
talk
about
the
upcoming
gitlab
13.4
release
and
what
the
editor
group
is
going
to
be
working
on.
So
I'm
going
to
share
my
screen,
we'll
dive
through
a
few
issues
and
kind
of
update
progress
on
a
few
of
the
other
things
we've
been
working
on.
So
let
me
get
that
started
here.
A
What
we've
got
up
on
the
screen
right
now
is
the
planning
board
that
we're
using
it's
broken
up
by
our
back
and
front
end
and
ux
teams
and
what
they'll
be
working
on,
and
so
I
just
wanted
to
highlight
a
couple
things
sort
of
broadly
in
here
we're
working
on
a
couple
bugs
inside
of
the
web
ide,
and
one
of
these
in
particular
that
I
wanted
to
highlight,
was
based
on
a
feature
we
just
released.
A
So
we've
just
released
a
feature
for
real-time
feedback
for
editing
the
gitlab
ci
yaml
file
inside
of
the
web
ide.
A
Unfortunately,
we
pulled
it
from
a
third
party,
and
so
we've
got
a
on
gitlab.com
there's
a
sort
of
a
course
or
csp
issue
with
accessing
that
content,
so
we'll
be
fixing
that
bug
in
13.4
it
should
deploy
to
getlab.com,
I
think
relatively
early
and
so
we'll
get
that
resolved
and
get
that
feature
back
on
track.
It's
highlighted
some
other
things,
as
we've
continued
to
work
through
custom
schema
that
we
might
be
supporting
and
some
others.
So
we've
got
some
ideas
on
how
to
fix
that,
but
sort
of
important
bug
to
keep
progressing
along
here.
A
A
A
I
don't
think
we'll
turn
that
feature
flag
on
by
default
for
gitlab
self-managed,
but
the
bulk
of
the
code.
That's
required
to
do
this
should
be
inside
of
the
package
release.
So
if
you
wanted
to
try
that
one,
you
would
be
able
to
do
that
at
the
end
of
13,
before
we'll
update
this
progress
section
here
and
the
epic
for
snippets
of
multiple
files
and
I'll
link
all
of
this
below
in
this
video
but
you'll
be
able
to
take
a
look.
A
Some
of
the
things
I
think
we've
gone
over
before
is
sort
of
what
the
edit
fields
will
look
like
for
when
you're
doing
this
and
what
that
might
look
like
for
up
to
10
phone
calls
and
sort
of
how
that'll
be
rendered
out,
and
so,
like
I
mentioned,
we're
nearing
the
end
of
this,
looks
like
we'll
be
able
to
test
them
thirteen
four.
So
I'm
really
excited
about
this.
A
I
think
this
is
sort
of
that
next
level
of
things
that
we've
been
trying
to
get
across
the
board,
with
snippets
and
being
so
close
feels
really
good
on
that
another
one
that
I
wanted
to
highlight
that
we've
been
working
on
sort
of
in
the
background
over
the
last
several
releases
is
changing
out
our
editor
for
what
we're
calling
editor
light,
which
is
based
on
monaco
for
sort
of
all
of
our
editing
experiences
inside
of
gitlab,
and
so
historically.
Gitlab
has
had
two
different
technologies
that
represented
our
editor.
A
One
technology
was
used
in
the
web
ide
and
one
technology
was
used
in
sort
of
other
single
file
areas
we're
moving
all
of
that
to
be
based
on
the
technology
that
our
web
ide
uses.
So
we
can
extend
some
of
the
features
that
we've
built
for
the
web
ide
specifically
back
into
these
other
editing
experiences
across
gitlab,
so
you'll
start
to
see
this
take
place
as
we
look
at
how
we
could
refine
editing,
experiences
for
gitlab,
ci
or
ending
experiences
inside
of
merge
requests
and
other
things
like
that.
A
So,
if
you're
interested
in
reading
about
sort
of
where
we're
thinking
our
editor
is
going
to
go
I'll,
put
a
link
to
the
web
ide
strategy
below
this
video
and
you
can
see,
but
this
is
sort
of
a
foundational
piece
to
get
us
there,
and
so
we've
already
done
this
for
the
snippets
editor,
we've
done
it
for
the
blog
editor,
so
the
main
kind
of
single
file
editing
experience
that
you
might
experience
in
a
repository
and
then
the
last
place
we've
got
which
we'll
be
tackling
in
1304,
is
in
the
cicd
edit.
A
So
if
you
were
to
try
and
go
into
the
pipelines
view
in
lint,
that's
where
you
would
find
this
editor
in
this
item
here
we've
talked
about
it
multiple
times.
There
will
be
another
one:
the
13
three
release
post
that
talks
about
it
again,
and
this
is
really
it
brings
sort
of
syntax,
highlighting
preferences
and
some
code
completion
and
intelligence
around.
A
The
last
thing
I
want
to
talk
about
was
implementing
the
web
id
button
in
the
diff
tab
of
a
merge
request,
and
so
this
very
small
iteration
that
we're
taking
to
sort
of
make
the
web
ide
more
present
in
merge
requests
and
we've
got
plans
to
further
integrate
the
web
ide
and
merge
requests
like
I
said.
Those
will
be
in
the
direction
page
that
I'll
link
down
below
this
video,
but
this
is
sort
of
a
baby
step
of
getting
the
web
id
more
present
there.
A
And
what
we'll
be
doing
here
is
adding
a
web
id
button,
and
you
can
see
that
here
on
the
diff
tab,
and
so,
if
you
had
a
merge
request
today,
the
only
way
to
actually
open
the
web
ide
is
to
go
to
the
overview
scroll
through
the
description
and
find
that
web
id
button,
but
oftentimes
when
you're
reviewing
a
merge
request
or
looking
at
feedback
for
a
merge
request,
or
you
want
to
go.
A
Make
that
review
the
context
of
sort
of
all
of
those
files
and
all
of
the
changes
that
you
need
to
make
are
really
important
and
the
a
good
way
to
see
that
can
be
in
the
web.
Ids,
particularly
if
you
want
to
make
a
change
or
add
an
edit
if
you
might
be
collaborating
or
that
or
you're
the
original
author
of
an
mrn.
A
So
once
you're
in
the
diff
you
being
able
to
scroll
or
being
able
to
quickly
access
that
web
ide
button
and
open
an
editor
where
you
can
make
those
changes,
we
think
that's
a
really
great
first
step
to
making
that
that
experience
more
tightly
integrated.
So
that's
what
the
editor
group
has
coming
up
for
thirteen
four.
A
You
can
also
check
out
what
we've
got:
13
3,
that
release
posts
will
be
coming
out
on
the
22nd
of
this
month,
so
excited
to
see
everything
in
gitlab,
13,
3,
but
I'll
put
links
to
everything.
We've
talked
about
in
the
video
down
below
and
if
you
have
feedback
on
anything,
please
feel
free
to
reach
out.
There's
contact
information
on
all
the
direction
pages
or
you
can
find
me
on
gitlab.com
thanks.