►
Description
Some distribution team members share their work todo scripting for other team members
A
A
Hi
everybody
today
is
March,
2nd
2023.
It's
distribution
demo
today
we're
talking
about
the
productivity
tools.
Basically,
it's
the.
How
do
we
track
our
work
and
our
weekly
reports
kind
of
a
thing
and
things
all
things
related
and
it
seems
like
we
do-
have
several
implementation
within
our
teams.
So
the
point
was
to
share
the
implementations,
make
everybody
aware
that
they
exist
and
maybe
you
know
kind
of
inspire
people
to
either
take
those
or
do
their
own
based
on
those
whatever
whatever
you
need
with
that
being
said,
Mitch
you
got
four.
B
So
the
one
that
I've
been
working
with
for
a
while
is
called
one-on-one
report
bot
effectively
when
I
started,
doing
101s
I
wanted
a
review
of
what
I
had
been
working
on
since
our
last
one-on-one,
and
so
originally,
this
report
would
just
use
the
gitlab
merge,
requests,
API
and
then
kind
of
sort
them
based
on
their
status
and
so
here's
an
old
example.
You
can
see
the
ones
that
had
in
Dev
in
review
merged
and
closed.
B
So
really
all
you
need
to
do
is
grab
an
API
token
and
your
user
ID
and
then
by
default,
it'll
search
back
last
seven
days,
but
that's
configurable
too,
and
then
it
really
just
prints
out
a
markdown
report
and
then
there's
an
optional
flag
to
pass
to
create
a
snippet
out
of
it
just
an
easy
place
to
dump
that
mark
down
table.
And
then,
if
you
want
to
search
by
any
specific
labels,
you
can
do
that
too.
Just
in
case
that's
relevant
to
your
workflow.
C
B
If
there's
anything
wrong
with
it,
you
can
always
edit
it.
It
comes
out
as
a
private
by
default,
so
you
can
just
edit
it
to
make
it
public,
and
then
you
kind
of
have
a
history
of
all
your
one-on-ones
to
go
back
to
which
is
nice
I'm,
recently
working
on
moving
over
to
the
events
API,
and
that
gives
you
a
little
bit
more
information
such
as
issues,
and
so
you
can
see
that
from
here.
B
This
is
one
of
my
more
recent
reports
Now
by
each
project,
I
get
a
list
of
what
I
did
with
issues
and
what
I
did
with
merge
requests,
including
approved
closed
and
merged,
and
it
splits
It
Up
by
project
like
that
and
then
typically,
what
I
do.
If
there's
anything
I
want
to
call
out
I'll,
just
since
it's
just
markdown
I'll,
just
bold
it
so
I'll
put
a
couple
asterisks
on
either
side
of
each
line.
That
I
want
to.
B
Just
kind
of
gives
an
overview
of
what
I
was
working
on
that
week
to
understand
the
command
line.
He
just
basically
called
go
run
or
if
you
want
to
use
the
docker
image,
you
can
do
that
too.
That's
the
flags
and
it
prints
this
out.
So
this
is
what
it
looks
like
in
the
back
end.
If
you
don't
create
the
snippet
out
of
it,
that's
really.
It.
C
A
No
I,
just
like
I
think
you
will
see
that
it
is
possible
like
what
I'm
doing
versus
what
Mitch
was
doing,
and
it's
just
jumping
a
little
bit
ahead
and
I'm.
Basing
my
reports
on
events
rather
than
specific
items,
so
I
get
everything,
but
there
are
some
gotchas
so.
B
The
object
on
my
to-do
list
right
now
is
like
including
commenting
on
an
issue
without
closing
it,
because
right
now,
it's
just
basically,
if
you
open
or
close
one,
but
what,
if
you're,
just
kind
of
commenting
on
one,
for
example
like
a
triage
issue
or
reviewing
a
merger
Quest
without
approving
it,
so
that
you
go
through
and
leave
some
comments
or
suggestions,
but
you
didn't
yet
approve
it.
B
That's
not
reflected
yet
so
just
finding
different
ways
to
work
with
the
events
API,
so
I've
just
been
tinkering
with
that
in
different
approaches
to
that
to
make
as
robust
of
a
report
as
possible,
but
it's
already
an
improvement
over
the
Mr
API,
because
that
was
only
at
Mars
at
least
now
we're
getting
issues
but
I
definitely
want
those
components,
I'm
sure
there's
other
things
missing
too,
but
that,
like
you
pointed
out
I'm
sure,
is
missing
right
now,.
A
All
right
so
I'll
with
that
being
said,
I'll
try
to
share
my
screen.
My
computer
is
misbehaving
today,
so
I
hope
it's
gonna
work
sure
there
we
go
okay.
So
what
I'm
using
is
like
I,
said
I'm
using
the
events
and
I'm
parsing
them
and
I'm
sorting
them.
So
here's
by
weekly
reports
project
that
does
all
that
stuff
and
it
uses
under
the
hood.
It
uses
my
old
jail
workflow,
the
stuff
that
I
have
been
producing
before
I
started
to
work
more
with
the
G
lab
CI.
A
So
there's
that
script
weekly
report,
which
is
basically
it
grabs
all
the
events
before
or
after
they,
but
then
it
has
that
what
exactly
what
Mitch
was
referencing
aggregate,
those
events
into
more
digestible,
something
and
then
from
there.
A
Everything
else
is
built.
So
this
is
what's
under
the
hood
and
but
I
did
go
a
little
bit
further
than
that.
So
this
is
what
it
looks
like
in
the
end.
A
That's
my
report
for
all
the
activity
for
the
week
and
then
it
also
does
do
the
work
plan
and
work
plan
is
basically
everything
that
is
currently
assigned
to
me
and
what
I
have
done
is
I
just
pick
out
the
items
within
the
two
like
within
several
Milestones,
because
we
currently
have
previously.
We
just
had
one
Milestone
that
we
worked
on,
but
right
now
we
do
have
this
next
one
to
three
releases,
so
I
had
to
expand
whatever
I
had
to
actually
process
multiple
Milestones.
A
So
it
does
that
now
so
the
stuff
that
you
see
here.
Actually
it
also
works,
except
for
the
reporting
reporting
takes
a
bit
of
time
for
all
the
querying
and
everything.
So
that
is
done
from
my
Pipeline
on
schedule
and
we
can
actually
take
a
look
at
what
it
produces
generate.
Md
there
should
be:
oh,
no
I
only
saved
markdown
I
didn't
save
the
Json
that
it
produces,
but
basically
yeah
all
of
those
tools.
They
use
the
API
to
the
best
of
their
ability.
A
The
events
I
have
expended
because
events
only
gives
you
the
pointers
to
the
Mrs
issues
and
stuff
like
that.
So
you
have
to
re-resolve
it
and
fetch
the
data
from
that,
so
that
one
I
had
to
go
a
little
bit
deeper
on,
but
otherwise
I'm
using
all
the
other
tools
on
the
command
line
as
well.
So,
for
example,
we
can
do
Milestone,
510
I
can
do
same
imrs
and
I
can
output
it
as
text
and
it'll
just
create
for
any
Mrs
that
I
am
working
on
for
the
Milestone
510.
A
A
A
It
drops
a
lot
more
and
it's
like
the
stuff
that
doesn't
have
any
milestones
or,
if
I
wanted
to
do
something.
Fancier
I
can
actually
do
it
by
the
label
as
well.
A
Yeah,
it's
labeled,
so
none
of
my
Milestone
like
work,
isn't
deliverable
right
now.
But
if
I
yeah
I
guess
that's
what
it
is,
but
if
I
go
for
example,
for
my
reviews,.
A
And
that's
my
work,
so
it
iterates
over
everything
that
I
have
the
to-do
list,
the
reviews
and
the
Mars,
and
obviously
they
can
overlap.
I
did
not
do
deduplication
here.
So
if
the
issue
references,
Mr
or
vice
versa,
it's
just
gonna.
Be
there.
That's
all
there
is
to
it,
so
that
stuff
is
basically
all
a
bunch
of
show
Scripts
over
the
Geo
Glam
CI,
it's
G
lab
CLI.
A
It
actually
can
use
either
g-lab
or
geoflow
and
both
of
them
have
their
own
money
limitations.
That
I
listed
in
our
notes
and
both
tools
like
Maya
GL
flow,
has
a
problem
with
pagination
when
it
comes
to
API
calls,
because
it
doesn't
paginate
them
and
the
g-lab
CI
g-lab
CLI
is
actually
having
a
reverse
problem.
The
only
thing
that
can
be
unpaginated
is
the
API
call
so
I'm,
using
mostly
that
I
tried
to
use
graphql,
but
graphql
does
not
fetch
everything,
so
that
was
a
bust
for
me.
A
One
thing
that
to
Remember
When,
You're,
Building
or
using
any
of
those
tools
is
that
they
will
pick
up
the
confidential
issues,
so
you
have
to
and
if
you're
working
on
something
security
related,
and
we
don't
want
that
to
be
exposed
to
public,
you
may
want
to
try
to
either
filter
them
out
or
just
publish
instead
of
publishing
the
whole
thing,
maybe
publishing
just
a
reference
to
the
issue
so
that
if
a
person
doesn't
have
access,
they
won't
get
any
information
out
of
that.
A
Yeah
I
already
mentioned
that
reports
and
plans
are
different,
like
reports
is
something
historical
and
they
take
up
time.
So
I
don't
have
anything
in
command.
A
Generate
them
in
command
line
as
well
same
command,
but
it's
just
it's
not
as
useful.
The
plans
are
a
lot
more
useful
to
me
because
I
use
it
now
on
The
Daily
when
I'm,
just
okay,
what
am
I
working
on
today,
so
I,
just
pull
up
and
just
okay
I
want
to
work
on
my
Mrs,
so
I'll
just
pull
up
this.
Do
the
Mrs
hours
of
gold?
No,
it
says:
okay,
nothing
on
deliverables!
I!
Don't
have
to
complete
anything
today,
yeah
another
guy
I've
faced
is
the
definition.
What
is
current
Milestone?
A
So
what
I'm
doing
I'm
just
pairing
the
API
for
the
milestones
for
the
gitlab,
org
and
I,
then
sort
them
as
if
they
were
all
versions
stuff
that
cannot
be
mapped
to
number
I
just
create
a
dummy
version
999999.
A
So
it
goes
way
below
and
then
I'm
just
grabbing
the
first
from
the
top,
the
current
the
youngest
version,
so
to
speak,
the
one
that
is
closer
to
the
top
and
that's
how
I
determined
that
you
know.
1510
is
my
current
thing,
so
you
will
one
thing
that
I
did
not
show
in
my
report
for
the
word
plan.
The
way
I
generate
that
section
I'm
actually
but
oh
yeah
I
did
show
me
that
that
I
do
put
the
Milestone
next
to
the
item.
A
And
I
think
that's
about
that.
Any
questions.
A
Oh
glad,
you
asked
I'm
being
lazy,
I'm
just
generating
the
MD
file
and
then
I'm
doing
the
this
guy
and.
A
Because
pages
also
allows
like,
since
I'm
publishing
to
the
pages.
When
you
define
the
project,
you
can
Define
it
as
private.
So
it's
not
visible
to
anybody
else,
because
I'm
not
filtering
out
like
I
mentioned
the
confidential
issues,
I,
don't
filter
them
out.
So
I
went
the
route
of
I'll,
just
publish
everything,
but
I'll
make
it
private
between
myself
and
my
manager,
or
whoever
else
wants
to
see
that
I
can
include
you
guys
in
my
project.
That's
no
problem
but
yeah.
That
was
one
way
of
dealing
with
that.
A
B
A
You
can
fetch
them
from
the
pipelines
really
I
I
don't
store
because
I
always
publish
them
to
the
same
place.
If
you
can
see
if
I
don't
know,
this
one
is
actually
I
wanted
to
show
you
the
new
format,
because
I
added
this
this
little
section
just
yesterday,
but
typically
there
is
a
standard
link
to
it.
C
A
A
One
and
there's
only
one
yeah,
okay,
fine,
never
mind
I'll
sort
it
out
later,
but
yeah
only
one
is
being
published
to
the
pages
and
the
rest
of
them
are
just
accessible
from
the
pipelines.
That's
all,
and
in
pipelines
it's
easy
to
kind
of
grab
them
as
they
are
all
scheduled
ones.
A
So
source
from
schedule.
A
Yeah
so
kind
of
early
morning.
A
C
C
Yeah
I
would
just
add
that
I
found
the
both
projects,
really
cool
I've
been
doing
similar
stuff,
but
manually,
not
automated
at
all,
but
I
have
like
the
the
habits
of
doing
this
for
a
year
now
and
like
it
really
helps
me
like
when
I
do
self-assessment
on
those
periodic
assessments,
you
know
like
to
go
back
to
those
and
see
what
they
can
relate
to
GitHub
values
and
those
kinds
of
things.
C
I
remember,
I
was
doing
the
way
I
do
it
like
I,
keep
track
of
a
very
big
issue
on
a
gitlab,
then
I
every
week,
I
just
like
keep
updating
that
issue
manually
and
I
can
see
how
this
can
help
me
in
my
process,
but
I
feel
like
some
kind
of
it
needs
to
be
also
or
another
needs,
but
I
would
like
to
have
something
that
is
also
like
very
searchable.
C
You
know
that
you
could
like
search
for
periods
and
likes,
because
I
want
to
check
what
I
did
for
the
last
six
Milestones
so
and
there.
A
You
can
actually
do
that.
The
the
reporting
that
I
have
here
I'll
try
to
show
you.
Where
is
this
thing
there?
A
A
And
if
you
want
to
run
it
from
the
command
line,
because
that
will
give
you
even
more
kind
of
control,
but
then
you'll
have
to
invest
into
setting
up
the
GL
workflow.
That's
a
python
project,
so
you'll
have
to
install
the
dependencies
and
say
things
like
that,
but
it
can
actually
do
the
Json
output
and
it
can
format
it
differently.
You
can
actually
because
the
default
here
is
where's.
My
weekly
report
right
there,
so
aggregate
breathe.
A
You
can
actually
do
counts
on
each
event
for
each
specific
project
or
you
know
whatever
you
were
doing,
which
means
that
you
will
have
some
sense
of
weight.
How
much
time
did
you
spend
there?
It's
not
precise,
but
it's
something.
C
A
C
A
Hearing
nothing,
oh
somebody
will
be
hitting
the
stop,
recording,
that's
it
for
today.
Thank
you.
Everybody.