►
From YouTube: Realtime Feedback of .gitlab-ci.yml in the Web IDE
Description
Introducing realtime feedback on .gitlab-ci.yml files in the Web IDE through JSON Schema.
Original Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/218472
Proposal for GitLab hosted Schema: https://gitlab.com/gitlab-org/gitlab/-/issues/218473
A
Hi,
my
name
is
kai
armstrong,
I'm
the
product
manager
for
the
editor
group
in
the
create
stage
here
at
gitlab,
and
I
wanted
to
show
off
a
new
feature
that
we've
got
coming
out
in
13.due
to
get
13.2
to
github.com
and
available
via
a
feature
flag
to
self-manage
instances.
We'll
talk
a
little
bit
about
why
why
it's
buying
a
future
flag
search
for
the
end
of
this,
but
I
wanted
to
show
off
the
feature
first,
so
I'm
gonna
share
a
window
here,
I'm
going
to
open
up
the
web
ide.
A
What
I've
got
is
a
blank
gitlab
ci
yaml
file,
and
so
this
is
a
way
to
configure
gitlab
ci
to
do
a
variety
of
things.
One
of
the
things
that
I
could
do
is
I
could
choose
a
template
here
that
I
want
to
use.
So
maybe,
if
I
want
to
do
a
hugo
site,
I
could
do
that
paste.
This
in
this
is
great.
That
feature
has
been
here.
A
What
I
want
to
show
you
is
a
new
sort
of
real-time
feedback
and
sort
of
lending
that
we've
added
based
on
json
schema,
and
so
what
this
will
do
is,
as
I
type
in
this
file,
you'll
notice
that
I'm
getting
sort
of
more
auto-complete
data
than
I
would
have
before.
This
is
because
we
now
know
about
this
file
and
some
of
the
types
of
properties
that
you
might
be
doing
and
how
to
do
those
and
so
we're
getting
this
autocomplete.
A
One
of
the
other
things
you'll
notice
is
that
currently
this
isn't
valid
syntax
right.
So
I'm
getting
this
underline
this
little
squiggly
line,
underneath
if
I
hover
this
and
come
back
up
to
it,
oh
we'll
see,
then
I
get
this
note
on
the
y,
and
so
it
says
the
gitlab
ci
configuration
tells
me
why
we
link
out
to
some
docs
that
can
help
you
do
this
and
we
tell
you
sort
of
you
know
what
the
error
is
and
why
that's?
Why?
A
A
The
the
pages
one
for
hugo
just
so
we
can
kind
of
go
through
some
of
these.
The
next
one
would
be
like
variables
and
again
you
can
see
that
provides
an
autocomplete.
It's
showing
me
that
currently,
this
is
invalid.
Syntax
again
telling
me
why
it's
telling
me
that
there's
sort
of
two
errors
here
we'll
go
ahead
and
tab
complete
through
that
you
can
see
it
automatically.
A
Tab
completes
drop
me
down
to
the
next
line,
which
is
great
because
then
I'm
already
ready
to
continue
typing,
and
I'm
just
going
to
do
something
here,
I'm
going
to
sort
of
misspell
this
and
then
move
on
right
and.
A
There
was
an
error:
it
seems
to
come
away,
which
is
not
okay,
but
let
me
fix
typo
there,
we'll
keep
going
we'll
do
the
test,
one
see
it
until
we
put
that
semicolon
or
that
colon
just
tells
us
that
these
aren't
correct
yet
test
I'll.
Just
script,
you
go,
let's
say,
accept
master
and
if
you
come
back
up
and
if
I
were
to
like
replace
a
couple
characters,
you'll
see,
I
throw
errors,
sort
of
up
the
chain
here
and
so
we've
seen
script.
Now
this
used
to
say
script.
A
It's
not
showing
the
error
saying
this
property
scpt
is
not
allowed
and
then
this
one
is
saying
that
it's
missing
a
property
script
and
so
that
sort
of
helps
inform
that
I
should
go
down
here.
Fix
this.
A
I'm
just
going
to
copy
the
last
little
little
bit
in
here
and
we'll
see
that
now,
we've
kind
of
rewritten
a
completely
valid
file,
but
we
along
the
way
we
sort
of
got
that
help
and
feedback
that
we
needed
to
get
through
that,
and
so
we're
really
excited
about
providing
sort
of
this
real-time
feedback,
while
you're
working
on
your
gitlab
ci
files.
A
Inside
of
the
web
id
in
133
we're
going
to
start
looking
at
supporting
custom
schema,
so
maybe
you've
got
a
different
file
type
specific
to
your
project
or
something
that
you
work
on,
that
you
want
to
define
a
schema
for
and
then
provide
some
that
feedback
and
those
additional
details
to
help
people
write
those
files
or
contribute
to
your
project,
and
so
we'll
be
looking
at
those
things.
A
So
that's
a
quick
preview
of
what
we've
got
coming
out
in
132
again,
I
said
you'll
be
able
to
find
this
on
gitlab.com
we're
not
going
to
release
this
on
self-managed
by
default,
and
the
reason
for
that
is
currently
the
schema
file
that
we're
using
is
coming
from
a
popular
open
source
project
called
schema
store.
It's
a
third-party
service
that
you
would
make
a
call
out
to
to
retrieve
that
schema.
We
didn't
want
to
turn
that
on
by
default
and
self-manage
and
have
self-managed
instances
make
a
call
to
this
third
party
by
default.
A
There's
an
open
issue,
I'll
link
it
down
below
the
video
to
have
a
bundled
version
included
inside
of
gitlab,
that
you
could
call,
or
a
gitlab.com
at
least
hosted
version
of
the
file
so
that
we
could
reference
that,
and
so
that
might
be
the
first
steps
that
we
take
there
I'll
link
that
issue.
If
there's
something
that
you're
interested
in
then
please
you
know,
leave
a
comment
on
that
issue:
upload
it
and
that'll
help
us
decide
where
we,
where
we
can
stop
that
in
an
upcoming
release.