►
From YouTube: 2022-06-30 Working Group: Merge Request Report Widgets
Description
Weekly call for the working group Merge Request Report Widgets
Agenda:
https://docs.google.com/document/d/1bcch8UUkwmgEHFolTWDrQFJtUiiXlv_yQFAGwSSDSUE/edit
A
And
we're
live,
welcome
everybody
yet
another
weekly
meeting
for
the
merge
request,
report,
widgets
working
group
and
let's
go
and
start
with
the
initial
checklists.
Where
do
I
have
it?
I
just
had
it
here:
okay,
I'll
just
do
it
by
heart.
While
I
open
this,
so
are
there
road
blockers?
Are
the
blockers
solved?
A
I
believe
so
I
don't.
I
don't
know
of
any
blockers
to
roll
out
right.
Okay,
just
like
on
the
wedding
waiting
for
everybody
to
speak
or
forever
hold
their
piece
feature
flag
enabling
production.
Yes,
it
is,
and
I'll
add
the
detail
of
globally
enabled
savas
is
joining,
so
it's
globally
enabled
right
now,
not
just
the
not
just
the
specific
projects.
A
Every
project
on
github.com
currently
has
it
the
merge
requests
to
to
make
the
feature
flag
default
is
being
prepared,
should
be
open
tomorrow
and
we
don't
know
exactly
what's
the
timeline
there,
we
want
to
open
it
so
that
we
can
start
looking
at
the
qa
test
and
see
if
anything
is
broken.
If
we
need
to
fix
anything,
but
phil
should
be
opening
that
either
today
or
tomorrow
and
sharing
it
on
the
slack
channel.
So
we
can
all
take
a
look
to
see
if
anything
needs
move.
So
it's
getting
close.
B
Questions
there
yeah
quickly,
when
was
the
flag
enabled
globally
and
have
been
any
issues
reported.
That
is
a
great
question.
A
Try
to
find
when
he
checked
the
check
box.
Oh,
I
actually
just
opened
the
merge
request
to
make
it
a
default
five
minutes
ago.
I'll
share
the
link.
I
think
I
think
it
was
enabled.
Three
days
ago
june
27th,
I
haven't
heard
any
feedback,
any
complaints,
but
maybe
I
missed
it.
So
that's
we're
going
to
keep
it
a
while
open.
So
for
now
we
just
want
to
get
ahead
of
ourselves
and
start
looking
at
the
state
of
the
future
flight
default
on
that's
good.
C
Question
what
happens
when
we
enable
the
feature
flag
and
the
individual,
mr
widget,
is
not
enabled
so,
for
instance,
security
rigid,
the
old
one
will
be
displayed.
Did
we
test
it.
A
A
I
think
that's
part
of
the
dri
checks
that
that
phil
pinked,
so
hopefully,
if
you
have
it,
please
make
sure
that
it's
working
correctly,
I
think
yannick.
There
was
an
issue
with
one
of
the
feature
flags
that
we
had
to
fix
it
at
the
very
last
minute.
Wasn't
it.
B
Yes,
that's
why
I'm
that's
why
I
was
just
asking
for
the
timing,
so
I
just
closed
out
the
blocker
for
the
enabling
yesterday,
but
it
is
a
huge
relief
for
me
that
you
mentioned
that,
because
I
I
introduced
phil
to
the
problem
before
I
went
on
pto.
So
if
phil
was
the
individual
to
enable
it
globally,
I
am
very
certain
that
he
probably
checked
it
and
just
didn't
close
the
issue
so
yeah
it's
close
now.
We
should
be
good,
so
no
worries
good
stuff.
A
Good
stuff
so
yeah,
it
feels
like
we're
we're
on
the
verge
of
having
this
available
for
customers
as
well.
I
think
they're.
So,
apart
from
the
usual
channels
to
receive
customer
complaints
like
zendesk
and
all
this
stuff,
I
think
we
just
followed
the
regular
procedure
and
just
announced
that
the
feature
flag
is
being
turned
on
that
sort
of
thing,
and
hopefully
something
comes
along:
the
pipelines
of
user
reports.
Customer
reports
we'll
hear
it
on
the
grip
fine.
A
So
it's
going
to
be
exciting
to
see
if
we
release
it
on
15
2,
then
so,
if
we
make
it
to
fault
on
15
2,
then
we'll
probably
just
keep
our
eyes
up
our
eyes
open
and
ears
peeled
to
to
see
if
any
feedback
is
coming
through.
The
customers.
D
E
Actually,
I
just
approved
the
reviewer,
mr
for
that,
so
it's
off
to
maintain
a
review
and
the
bug
was
like
an
edge
case,
but
I
think
in
the
last
meeting
we
discussed
that
technically
the
there's
a
workaround,
let's
refresh
the
page,
so
it
wasn't
a
blocker.
E
But
my
personal
feeling
is
that
if
we
have
a
little
bit
of
time
left
to
to
merge
that
merch
request
in-
but
you
know,
I
think,
the
by
the
lab's
official
criteria,
the
work
around
is
refresh,
so
it
shouldn't
be
a
blocker
there's
just
the
conclusion.
D
Okay,
and
was
that
happening
with
all
repos
or
just
our
gitlab
project,.
E
No,
that
bug
would
affect
everything
on
the
global
rollout
so
beyond
just.com.
If
we
don't
wait
for
that,
but
like
I
said
it
it,
the
team
feels
different.
You
know
people
can
speak
up,
but
the
the
mr
should
be
landed
shortly
soon.
So
if
it
does
go
out
now,
let's
say
we
turn
it
on
globally
for
everyone
now,
the
mr
to
fix
that
should
be
rolling
out.
You
know
today's
thursday,
I
mean
at
the
latest
earliest
next
week.
A
It's
globally
on
the
the
pending
thing
is
defaulting
on,
so
that
will
be
going
to
customers.
That
would
be
the
difference.
The
the
reason
there,
the
the
choice,
just
so
that,
for
the
recording
sake,
is
that
the
workaround
was
easy.
Wasn't
it
wasn't
too
much
of
a
workaround
and
we'd
rather
receive
more
feedback
on
the
edge
cases
that
other
projects
might
be?
Having
that
we
don't
have
on
our
project,
so
we
decided
to
go
on
with
the
robot.
A
So
going
on
working
group
wrap
up
check.
Are
the
widgets
released
kinda,
I'm
gonna
say
yes,
because
for
for
github.com,
pending
default
default
on
so
for
github.com
customers
for
them
it's
indistinguishable,
whether
it's
default
or
not,
and
for
customers,
then
it's
not
released
so
yes4.com
no
for
customers
in
the
next
step,
documentation,
reviewed
and
complete.
A
F
Yeah,
I
don't
know
if
it's
an
announcement
or
a
discussion
there
wasn't,
I
didn't,
feel
good
about
it
either
way,
but
there's
a
bug
in
all
of
the
default
telemetry
in
that
you
can't
dynamically,
create
events
to
be
sent
to
service
ping
unless
all
of
the
like
service
ping
stuff
knows
that
those
events
are
supposed
to
be
coming.
So
you
have
to
add,
I
don't
know
two
or
three
files
for
every
single
event
that
we
were
planning
on
sending.
F
A
There
we
go
nice-
I
I
haven't
seen
that
yet.
But
then
that
makes
sense,
then
we're
aligned
I'll
look
at
one
of
I'll
look
into
thomas
randolph's
availability
and
see
if
he
has
availability
on
15-2,
because
he
was
the.
A
F
F
No,
it's
not
a
there's,
no
failure
that
happens
it
just
when
the
service
ping
gets
generated.
It
won't
accept
event.
D
F
That
it
doesn't
expect
to
exist,
and
so
I
think
it's
fine.
F
I
think
we
just
need
to
get
all
those
files
created,
which
is
a
fairly
substantial
amount
of
work
and
then
on
there's
a
separate
issue
that
I
open
that
I
linked
that's
not
in
the
document
and
linked
to
that
issue
for
the
product
intelligence
group
like
just
see.
F
If
there's
ways
we
can
make
instrumenting
like
base
components
more
useful
without
needing
to
like
do
all
this
extra
work
every
time
a
new
widget
gets
at
it,
because
my
fear
now
is
that,
like
the
next
widgets
that
is
created
unless
these
people,
unless
whoever
does
that,
adds
all
of
the
event
files
for
it,
we
will
not
actually
get
instrumentation.
A
Yeah,
that's
what
I
was
asking
about
whether
the
code
should
check
for
the
existence
of
those
files,
because
then
we'll
be
able
to
catch
a
warning
of
some
sort,
whether
we
do
it
through
testing
on
ci,
whether
we
do
it
on
a
browser
console.
I
will
we
can
talk
about
it,
but
yeah
I'll
pass
it
on
to
thomas
and
I'll.
Let
him
figure
that
out.
Okay,
thank
you
for
the
heads
up.
A
A
Gotcha
moving
on
to
my
discussion
item
so,
as
I
mentioned
before,
one
of
the
things
that
we're
spending
was
the
exist
criteria
about
the
documentation.
I'm
just
trying.
I
was
trying
to
read
what
we
actually
wrote
in
the
documentation,
so
exit
criteria.
So
what
we
said
was
the
documentation
reflects
the
capabilities
of
the
shared
component
and
ensure
there
is
clear
documentation
written
for
extending
the
component,
so
I
pinged
both
samantha
ming
and
amy
qualls,
our
technical
writer
and
have
had
them
both
look
at
the
existing
documentation.
A
A
What
I
would
ask
for
everybody
who's
been
involved
with
the
working
group
before
considering
that,
as
like
a
check
mark,
is
take
a
look
yourselves
see
if
there's
anything
in
the
documentation
that
you
might
think
that
it's
missing
and
if
it's
not-
and
I
don't
hear
anything
from
you
I'll-
just
assume
that
you
agree
that
it's
fine
and
we'll
move
on
to
again
as
soon
as
the
rollout
is
complete
the
fault
on
we'll
start
talking
about
dismantling
the
working
group.
If
that
makes
sense,.
A
E
Sure
so
I
just
got
everything
I
think
I
need
for
back
end
for
license
compliance,
so
this
milestone
we're
hoping
to
turn
that
flag
on
and
this
flag
again
is
controlled
independently
for
the
global
one.
So
the
only
question
I
have
is
you
want
me
to
take
the
same
approach.
E
I,
the
team
used
for
the
all
the
other
widgets
like
first
enable
to
this
particular
project
on.com,
and
then
I
guess
I
don't
know,
I
guess
we
enabled
it
for
the
gitlab
project
first
and
then
we
did
like
the
dot
com,
rollout
and
then
self
managed.
You
want
to
take
the
same
approach.
I
guess
the
questions.
Do
you
want
to
take
the
same
approach
for
the
individual
widgets
that
have
their
own
flags
as
we
did
for
the
global
rollout?
And
if
so,
just
just
say?
Yes,
I
guess,
and
then
I
could
do
that.
A
I
would
I
would
say
that
by
default,
yes,
follow
the
same
procedure,
maybe
shorter
time
spans.
I
guess
because
it's
it's
a
more
specific
case,
but
yeah.
I
would
still
follow
the
same.
Go
one
step
at
a
time
yeah.
That
would
be
my
advice,
but.
E
And
I
did
have
one:
let's
see,
I
don't
I'm
trying
to
find
the
link
here,
one
technical
discussion,
just
more
of
a
fyi,
I'm
gonna
paste
the
link
here
so
last
earlier
this
week.
This,
mr,
is
it
adds
the
ability
to
do
polling
on
the
expanded
component.
So
we
have
right
now
the
polling
happening,
enable
pulling
will
pull
the
collapse
state
and
for
most
of
the
widgets
that
was
fine
license.
Compliance
is
a
bit
different
because
it
actually
was
one.
E
I
think
it's
the
only
component
that
has
two
endpoints
the
optimize
and
unoptimized
one
and
the
expanded
endpoint.
It
uses
the
same
caching
logic
as
the
collapse
endpoint.
So
on
the
initial
request
it
would
be
204
and
all
I
did
was
essentially
extend
the
functionality
to
kind
of
replicate
the
behavior
we
had
for
the
collapse
pulling
collapse
state
pulling,
so
it
made
it's
exactly
the
same.
E
The
new
flag
for
that
is
enable
expanded
pulling
as
opposed
to
just
enabling
pulling,
and
the
reason
we
want
to
to
differentiate
is
because
we
can't
assume,
if
you
enable
polling
for
one
that
you'll
be
pulling
both
endpoints,
because
some
of
the
widgets
derived
they're
expanded
they'd
rather
expand
the
data
from
the
collapse
data
and
do
one
request.
So
it's
always
kind
of
like
we're
trying
to
make
it
work
for
everybody
and
not
make
too
many
assumptions
so
anyway,
that's
there.
E
A
Yeah,
absolutely
it's
great,
because
now
now
every
individual
widgets
now
is
working
in
front
of
everybody.
So
if
you
turn
it
on
or
if
you
have
some
affection,
if
you
affect
the
code,
then
everybody
will
see
it
so
yeah
for
everybody
watching.
Please
proceed
with
that
awareness.
That
was
my
comment
on
the
above
point
and
with
that
we
exhausted
all
the
agenda
points
any
last
minute
editions.