►
From YouTube: GitLab CLI FY24 1 Year Plan
Description
Kai Armstrong, Sr. Product Manager, Create talks about the vision for the GitLab CLI and plans for the next year (FY24).
GitLab CLI Direction: https://about.gitlab.com/direction/create/gitlab_cli/
Current Research Survey: https://forms.gle/7C6JFjYTih8HqUHB6
- GitLab CLI Research: https://gitlab.com/groups/gitlab-org/-/epics/9517
- Refactor for Pagination: https://gitlab.com/groups/gitlab-org/-/epics/9419
- Authentication Improvements (OAuth): https://gitlab.com/groups/gitlab-org/-/epics/9363
A
A
So
let
me
start
with
our
vision
and
and
really
the
things
that
I
want
to
highlight
here
are
how
we're
thinking
about
the
CLI
and
what
we
want
it
used
for,
and
so
we're
really
looking
at
four
aspects
here:
we're
looking
at
configuration,
so
people
who
need
to
configure
projects
and
work
with
the
API
and
do
things
in
bulk
and
scripting
and
sort
of
that
style.
We're
looking
at
contributions.
A
So
if
you're
working
in
git
lab,
how
are
the
ways
that,
when
you
contribute
to
things
in
gitlab,
the
CLI
can
enhance
that
experience
for
you
automation
as
well.
So
maybe
you
have
tasks
that
you
run
on
a
regular
basis,
or
maybe
you
need
to
do
things
in
a
pipeline.
How
can
the
gitlab
CLI
sort
of
enable
those
things
for
you
and
then
flexibility?
We
want
the
gitlab
CLI
to
be.
A
You
know,
opinionated
in
what
it
can
do,
but
flexible
enough
that
it's
able
to
support
a
wide
variety
of
workflows
and
use
cases
in
sort
of
different
places,
so
we're
really
trying
to
strike
a
balance
between
those
two
things.
So
that's
really
how
we're
thinking
about
the
git
live
CLI
and
like
what
the
vision
is
for
it.
But
let's
talk
about
what
the
next
year
looks
like
for
us
in
terms
of
a
plan
and
so
over
the
next
year.
A
and
so
we're
still
learning
what
else
our
users
want
for
it
and
how
they're,
using
it
we're
currently
doing
a
survey
I'll
put
that
down
below.
So
you
can
fill
that
out
if
you
want
to
share
some
feedback
on
the
gitlab
CLI,
but
we're
really
trying
to
understand
these
existing
use
cases
and
looking
for
opportunities
to
sort
of
build
on
what
our
users
are
doing
and
making
those
things
easier
for
them
before
we
commit
to
anything
that
that
we're
really
passionate
about.
A
We
really
want
to
know
what
the
users
are
while
we're
in
the
progress
of
figuring
those
things
out.
We
are
working
on
a
couple
things,
and
so
one
of
those
is
paginated
results,
and
so
there's
a
lot
of
things
that
you
can
do
in
the
gitlab
CLI.
That
return
multiple
results
and
sometimes
pages
of
results.
You
might
list
issues
and
you
might
have
10
pages
of
20
issues,
and
so
some
commands
work
really
well
with
pagination
and
some
don't
inside
of
the
CLI.
A
And
so
we
want
to
just
bring
some
consistency
to
that
whole
experience
and
make
sure
that
you
can
expect
that
when
you're
using
the
gitlab
CLI,
if
results
can
be
paginated,
you
can
get
all
of
those
pages
of
data,
and
so
that
way
you
you're
not
questioning
whether
or
not
we're
giving
you
everything
back
every
time.
And
so
this
is
sort
of
a
broad
effort
across
the
CLI.
A
Authentication
is
a
big
challenge
for
for
all
kinds
of
tools,
but
in
the
CLI
it's
a
challenge
because
you've
got
to
create
a
personal
access.
Token
get
that
personal
access
token
set
up
in
the
CLI,
either
with
one
password
or
some
other
tool
to
keep
it
secure.
And
then,
then,
you
can
start
using
it
and
we
want
to
make
that
experience
easier
for
you
and
support
oauth,
where
you
could
just
auth
directly
from
the
CLI
to
your
gitlab
instance.
A
Have
all
the
tokens
and
credentials
returned
and
then
use
that
as
the
connection
mechanism
that
both
brings
ease
of
access
and
security
to
users
when
they're
using
the
gitlab
CLI?
So
that's
probably
the
next
thing
that
we're
going
to
look
at
over
the
over
the
course
of
the
year
is
really.
How
do
we
improve
that
onboarding
experience
and
oauth
will
be
a
big
piece
of
that
for
us.