►
From YouTube: GitLab 13.1 Kickoff - Create:Editor
Description
Highlights from the 13.0 Release:
- https://about.gitlab.com/releases/gitlab-com/#dark-theme-in-the-web-ide
- https://about.gitlab.com/releases/gitlab-com/#versioned-snippets
Upcoming items for the 13.1 milestone:
- Multiple Files in Snippets: https://gitlab.com/groups/gitlab-org/-/epics/2829
- Exploring Snippet permissions in Projects: https://gitlab.com/gitlab-org/gitlab/-/issues/16256
- EditorConfig Support in the Web IDE: https://gitlab.com/gitlab-org/gitlab/-/issues/23352
- Implementing Monaco for the Single File Editor: https://gitlab.com/groups/gitlab-org/-/epics/498 and https://gitlab.com/gitlab-org/gitlab/-/issues/198605
A
Hi
everyone,
my
name-
is
KY
Armstrong
I'm,
the
product
manager
for
the
editor
group,
in
the
create
stage
of
the
DevOps
life
cycle.
Here,
gillip
and
I
wanted
to
talk
about
the
upcoming
13.1
release
for
gitlab
and
what
the
editor
group
has
planned
and
so
I'm
going
to
share
my
screen
and
we'll
get
into
some
things.
First,
you
wanted
to
start
with
a
couple
things
that
I'm
really
excited
about
that
are
coming
out
in
13.0,
so
13
auto
we're
releasing
the
dark
theme
for
the
web
ID.
A
So
you
can
see
this
here
if
you're
on
github.com
and
you've
already
set
your
syntax,
highlighting
preference
to
dark
you'll
already
be
using
this.
So
I'm
really
excited
about
this
and
all
the
work
the
team
did
to
get
this
across
the
line,
so
take
advantage
of
that
once
you're
on
the
13
auto
release,
the
other
one
I
wanted
to
highlight
over
1300
is
version
snippets.
So
this
has
been
true.
A
Remember
all
these
other
kick-off
videos
I've
been
talking
about
version
snippets
and
version
snippets
and
how
we're
almost
there
it
is
here
and
it
is
launching
in
13.0
and
so
the
13.0
you'll
be
able
to
clone
a
snippet
and
they'll
be
backed
by
git
repository,
so
about
version
control.
So
we're
really
excited
about
that
and
that'll
bring
us
into
13.1
and
what
we're
going
to
talk
about
here,
and
so
I'm
13.1.
A
The
momentum
is
continuing
with
snippets
we're
now
going
to
start
working
on
introducing
multiple
file,
support
for
snippets,
and
so
since
its
are
really
valuable
in
sharing
pieces
of
content,
but
they
sort
of
have
an
issue
when
you've
got
to
share,
maybe
a
script,
and
then
the
log
file
that
that
script,
outputs
or
maybe
you're
trying
to
share
some
HTML
and
CSS
or
JavaScript
with
another
user,
because
we
are
snippets,
are
limited
to
one
file.
Those
things
don't
work,
so
what
will
be
starting
on
them?
13.1
is
a
lot
of
the
backend
work.
A
That's
going
to
be
required
to
bring
in
multiple
files
and
then
we'll
start
working
on
the
UI
components
to
introduce
this.
What
I've
got
up
on
the
screen
here
is
the
epic,
so
you
can
start
to
see
what
that
looks
like,
and
so
you
know
if
we
take
a
look
at
some
of
these
screenshots
and
a
list
of
files,
you'll
notice,
you
know
you'll
now
see
that
there's
multiple
files,
if
there's
more
than
one
or
we'll,
show
the
file
name.for.
A
One
user
is
able
to
edit
and
make
changes
to
that
snippet,
that's
the
original
author
and
so
we're
gonna
start
doing
some
investigations
into
changing
that
permission
model
and
what
the
broader
impacts
might
be
right
now
the
plan
is
to
adjust
snippets
inside
of
projects
to
just
follow
the
project
access
permission.
So
if
you
have
developers
who
are
able
to
push
code
and
in
a
project,
then
developers
in
a
project
would
be
able
to
push
to
that
snippet-
and
you
know,
there's
some
considerations
we'll
need
to
make
about.
A
Well,
what
if
we
don't
want
that
to
happen,
but
we
think
this
is
the
first
right
step
in
normalizing
these
permissions
and
how
we
like
do
that.
So,
if
you've
got
feedback
on
what
you'd
like
to
see,
there
I'll
make
sure
this
issues
down
below
in
the
comments,
and
you
can
take
a
look
at
that
and
provide
some
feedback
there.
A
Moving
on
to
editing
and
specifically
inside
the
web,
ID
we're
gonna
take
on
an
issue
to
support
the
editor
config
file
for
the
web
idea.
So
editor
config
is
a
standard
that
helps
with
coding,
style
and
file
formatting
for
specific
things
that
you
might
define
in
there,
so
you
might
define
tabs
or
spaces
or
how
many
you
know,
the
tab
width
or
how
many
spaces
you're
using
those
types
of
things,
and
so
we're
gonna
make
the
web
ID.
A
If
you
have
an
an
editor
config
file
defined
in
your
repository,
will
support
that
when
you
open
that
project
in
the
web
ID
and
we'll
apply
certain
some
of
those
rules
to
fill
your
files
in
there,
and
so
we've
outlined
here
in
terms
of
what
styles
or
what
rules
will
enforce.
What
we're
able
to
do
in
terms
of
tab,
width
and
whitespace
and
size
and
style
of
indents,
so
we're
gonna
work
on
delivering
this
in
13:1.
A
This
I
think
this
is
a
great
step
forward
for
teams
really
trying
to
be
consistent
about
how
they're
writing
their
code
and
what
those
files
look
like,
and
so
we're
excited
to
bring
that
to
you.
Well,
that's
what
I
want
to
touch
on
here
is
sort
of
our
editors
that
we've
gotten.
This
is
a
little
bit
of
back
in
technology,
but
our
web
ID
is
based
on
an
open-source
product
called
Monaco.
A
It
is
the
foundation,
the
editor
for
vs
code
and
a
lot
of
other
online
IDs
that
you
might
use
so
Monaco's
what
we
use
there,
our
single
file
editor.
So
if
you
go
into
repository
and
you
could
be
edit
button
menu,
don't
load
the
full
web
IDE
and
space
on
a
protocol
ace
we're
working
to
standardize
on
Monaco
for
all
our
editing
and
I
think
it
says
a
lot
of
advantages
and
maintainability
and
other
things,
but
as
a
user,
what
that
gets.
You
is
the
experiences
that
you
have.
A
You
know
for
things
like
editor
config
that
we're
working
on
or
all
of
the
syntax
highlighting
preferences
that
were
just
introduced
in
previous
releases.
All
of
those
things
will
be
standard
and
sort
of
all
the
editing
experiences
and
you
get
lab,
and
so
that's
really
what
we
want
people
to
have
when
you
go
to
edit
a
piece
of
code
inside
of
gala.
A
We
want
that
to
be
the
same,
no
matter
how
you're
doing
it
that
way,
all
the
tools
and
functionality
that
you
have
and
one
are
not
different
in
the
other
and
so
with
the
launch
of
snippets
version
snippets
in
13
Dada
we'd.
Already
we
replaced
that
editor.
That
was
the
first
place.
We
changed
the
editor
out
for
a
salon
ago,
and
we
will
highlight
some
of
that
and
really
expose
coming
up
and
13
about
some
of
the
benefits
that
you're
getting
there.
A
What
we'll
be
working
on
at
13.1
is
replacing
that
in
the
single
file
editor,
and
so
the
home
is
quickly
a
project
here
and
when
I
say
single
file
editor.
What
I'm
talking
about
is,
if
I
see
this
file
here
and
we
click
Edit.
This
is
a
different
editor,
the
actual
kind
of
text
area
where
I'm
editing
code.
Then,
if
I
were
to
go
back
to
this
project,
I'll
just
leave
this
and
open
this
in
the
full-blown
web
ID,
and
you
can
see
the
dark
web
ID
here
all
over
the
file
back
up.
A
But
so
what
we're
gonna
do
is
we're
going
to
standardize
these
things
so
that
I
would
have
had
a
similar
editing
experience
if
I
click
that
it
would
have
been
dark
with
my
preferences,
such
that
it
would
have
been
highlighted
much
more
like
this
than
than
the
other
syntax
highlighting
preferences
that
were
there
and
then
those
other
style
things
that
we've
talked
about
with
a
header
config.
Another
support
that
we
have
so
that's
what's
coming
in
13:1
I'll
make
sure
there
are
links
to
all
of
these
things
down
below
the
video.