►
From YouTube: GitLab 12.6 Kickoff - Ecosystem
Description
Kickoff page: https://about.gitlab.com/direction/kickoff/
Ecosystem Direction page: https://about.gitlab.com/direction/ecosystem/
We want to hear from you! Please ping @deuley in Issues, or reach out directly at pdeuley@gitlab.com
A
So
first
up
we
had
a
customer
request
for
an
API
endpoint
to
show
commits
ancestry.
So
the
request
was
to
clone
the
functionality
of
get
rev
list,
which
is
a
core
functionality
and
git
that's
been
around
for
a
while.
That
allows
you
to
see
a
list
of
Shaw's
between
one
commit
and
another.
So
this
shows
you
a
couple
of
things
specifically.
They
were
asking
for
the
topo
order
flag.
A
So
what
that
does
is,
if
you
look
at
the
numbering
on
this
list,
so
this
is
in
chronological
order,
so
one
two
three
four
five,
six,
seven
eight
right,
topo
order!
Does
it
topographically,
so
instead
it
would
return.
Eight
six
five,
three
seven
four
two
one
likes
showing
that
mapping
instead
of
the
chronological
order,
so
we'll
make
sure
in
the
flags
we're
going
to
be
including
the
topo
order
flag
adding
before
and
after
so
you
can
limit
across
a
span
of
time
and
then
it
will
respond
with
a
list
of
Shaw's
between
those
two
commits.
A
We're
also
looking
to
expand
our
API
to
have
a
route
for
project
services
that
are
enabled
on
a
project.
So
specifically,
what
that
allows
us
to
do
is
show
that
overall
list,
whereas
right
now
we
only
show
the
details
for
one
service,
so
this
will
enable
us
to
work
on
some
future
projects
that
we've
been
kicking
around.
We
want
to
improve
the
project
services
UI.
So
that's
the
page.
That's
called
integrations
on
a
project
that
page
is
pretty
simplistic
and
we'd
like
to
expand
it
with
more
information,
so
this
will
help
us
prepare
for
that.
A
We
also
want
to
create
an
overview
for
projects
that
have
that
service
enabled
so,
for
example,
getting
a
list
of
all
of
the
projects
that
are
using
the
Jenkins
integration
at
a
group
level,
or
all
of
the
slack
integrations
being
used
across
an
entire
instance.
So
we're
starting
work
on
this
API
route
in
preparation
for
other
things
that
we'd
like
to
enable
later
we're
also
looking
at
unfurling
Stack
Overflow
content
in
comments.
So
everybody
at
this
point,
I
think,
should
be
on
familiar
with
this
pattern.
A
Right
I
think
this
was
mostly
popularized,
or
at
least
credited
as
being
popularized
by
Twitter
unfurling
links
to
show
richer
content
has
become
a
really
common
pattern
and
there's
a
good
reason
for
it.
It
makes
it
much
more
readable
in
a
list
of
texts
right.
So
if
you've
just
got
this
link
and
Stack
Overflow
I
think
it
can't
be
understated
how
valuable
Stack
Overflow
is
to
developers
I'm
sure
all
of
us
have
at
some
point
copy
and
pasted,
and
the
answer
at
a
Stack
Overflow
and
moved
on
with
our
lives.
A
So
that's
a
really
valuable
resource,
this
little
link
and
by
leaving
it
as
just
a
link,
it's
really
easy
to
just
pass
through,
but
by
making
that
content
richer.
It
draws
the
eye
of
the
reader.
It
makes
it
easier
for
them
to
see
if
it's
valuable
right
so
showing
the
title
of
the
page,
showing
a
description
of
the
page
that'll
make
it
easier
for
customers
to
consume.
This
also
sets
the
stage
for
some
other
work.
We're
looking
at
doing.
A
We've
gotten
requests
for
embedding
things
like
zoom
calls,
metrics
errors,
pager
Duty,
logs,
Salesforce
customers
and
more
so
we've
got
to
start
somewhere,
so
Stack
Overflow
is
a
great
place
to
start.
This
will
allow
us
to
create
a
reusable
pattern
that
we
can
then
start
applying
to
other
components
where
we'd
like
to
and
for
a
leather
content.
A
A
We
need
to
add
a
remaining
project
services
to
our
usage
ping
in
12/5.
We
talked
about
this.
We
are
adding
more
of
the
project
services
to
our
usage
ping
data,
so
in
12/5
we're
adding
Jenkins
matter
most
and
the
custom
issue
tracker
services-
those
are
complete
and
are
in
there.
Now
we
want
to
add
more
of
these
services
to
12:6
and
then
over
the
next
few
iterations
we're
going
to
continue
to
add
them
until
all
of
the
project
services
are
represented
and
you
ping.
A
We
have
a
couple
of
bugs
that
had
high
impact
that
I
wanted
to
call
out
specifically
last
activity
field
is
not
being
updated
appropriately
when
someone's
using
the
API,
so
users
of
the
UI
in
their
in
their
user,
object
last
activity
fields
getting
updated
when
they
click
on
things
and
do
things,
but
if
they
make
calls
to
the
API
that
doesn't
get
reflected.
So
this
is
a
problem.
A
Obviously
this
is
already
a
bug,
but
it's
a
particular
impact
to
people
who
are
doing
things
like
automatically
D
provisioning,
inactive
users,
so
a
user
may
appear
to
be
inactive,
but
if
they're
using
us
through
the
API
they're,
actually
not
inactive
and
if
those
get
D
provision
that
could
cause
some
some
heartache
for
them.
So
we
need
to
fix
this
and
then
finally,
we've
got
a
problem
where
the
Jenkins
service,
if
it
fails
to
trigger
which
could
be
because
it
times
out
it
could
be
other
reasons
if
it
fails
to
trigger
the
Jenkins
pipeline.