►
From YouTube: New changes workflow in the GitLab Web IDE
Description
In GitLab 12.9 we removed the concept of staging from the Web IDE. Take a look at the new changes workflow and let us know what you think!
Issue: https://gitlab.com/gitlab-org/gitlab/issues/196609
Connect with me: https://gitlab.com/phikai
A
Hi,
my
name
is
Chiron
I'm,
the
product
manager
for
our
editor
group
in
the
create
stage
and
I
wanted
to
talk
about
a
change
that
we
made
and
get
a
12-9
to
the
way
we're
dealing
with
commits
inside
of
the
web
ID
or
change
files
inside
annoying.
So
let
me
share
my
screen
here.
Real
quick,
well
sure.
The
whole
screen
over
here
I've
got
up
over
here
is
a
walkthrough
that
we
did
back
in
January
and
I
kind
of
move.
The
slider
I'll
post
the
link
to
time
stamp
this,
but
can
I
quickly
watch
this.
A
A
And
so
what
we
just
saw
there
was
commit,
and
then
in
the
video
I
explained
that
we
automatically
state
changes
which
was
really
great,
so
we
switch
from
a
model
where,
when
you
made
a
change
in
the
web
ID,
you
then
had
to
like
explicitly
states
those
changes
that
cause
some
issues
that
sometimes
not
all
the
changes
would
get
stayed.
Sometimes
some
changes
were
staged
automatically
and
you
could
proceed
and
you
would
lose
things,
and
so
it
was
just
an
overall
confusing
process.
A
So
we
moved
to
a
model
where
we
automatically
staged
everything,
but
let
that
run
for
a
couple
of
months
just
to
see
if
there
was
any
feedback
about
how
that
would
work
or
what
kind
of
issues
people
light
right
at
you.
We
didn't
really
hear
anything
back
from
the
community.
We
didn't
hear
back
from
internal
gitlab,
which
he
uses
the
weather
I
eat
quite
a
bit
for
our
own
handbook
and
marketing
website.
A
A
You
know
what
change
the
whole
title,
what
I
say
no
more
staging,
so
this
is
really
interesting.
So
I've
made
my
change
I'm
ready
to
commit
this.
Let
me
commit
this
you'll
kind
of
already
notice.
There's
a
change
here.
This
is
one
change
file.
If
we
were
to
back
this
video
up
just
a
little
bit
more
good,
you'll
notice,
it
says
one
staged
and
zero
on
the
stage
changes
down
on
the
bottom
down
here.
So
now,
we're
just
saying:
there's
a
changed
file
when
I
click
commit
I.
A
Just
now
have
a
list
of
changes
and
I
can
either
commit
all
these
changes
or
I
could
discard
all
these
changes
versus
and
the
older
workflow.
We
still
could
stage
a
nun
stage,
various
files
and
do
other
things
commit
committing
to
master
new
branch
merchant
class.
All
that's
the
same,
but
really
what
we're
focused
on
is
this
new
changes
thing
here,
and
this
new
changes
is
really
designed
to
make
it
easier
for
users
to
make
a
change
in
the
web.
Id
commit
that
change
and
they
don't
need
to
understand.
A
What's
going
on
on
the
get
side
of
things
whether
we're
staging
or
on
staging,
they
don't
need
to
understand
those
things.
I
think
the
web
ID
is
a
place
where
we've
got
an
overlap
between
engineers
and
maybe
non
engineers
who
are
used
to
familiar
would
kind
of
get
workflows,
and
so
this
is
a
really
good
change
to
just
simplify
this
get
people
to
make
changes
in
the
web.
Id
commit
those
changes
and
either
create
a
branch
circuit
where
each
requester
commits
those
two
masters.
So
we're
really
excited
about
this
change
in
the
web
ID.
A
It's
kind
of
one
of
the
first
changes
we're
making
to
the
left
side
where
that's
really
dramatically,
impacts
things
here.
So
if
you've
got
any
feedback
on
it,
let
us
know
you
can
leave
a
comment
on
the
video
down
below
or
you
can
reach
out
to
me,
I'll
link
to
my
git
web
profile
and
find
me
and
tag
me
in
an
issue.
So
thanks
for
taking
a
look.