►
From YouTube: Meshery CI Working Group (June 22nd, 2020)
Description
Automating releases with GitHub PR Labels.
B
A
A
My
muscles
are
atrophying.
Actually
I've
just
been
sitting
in
this
freaking
chair
for
months
now,
and
it's
kind
of
sad
I'll
go
work
on
them
to
get
them
back
at
some
point,
but
it's
a
real
thing.
I
mean
I
think,
I'm
going
to
have
a.
I
think,
I'm
going
to
have
a
a
seat,
a
med
score.
On
my
I
mean
I
don't
have
a
bed
tour,
but
I'm
just,
but
I
mean
I
could
from
how
much
I
just
sit
here.
A
B
A
A
B
A
I've
seen
some
people
during
the
pandemic
they've.
Actually,
there
was
the
gal,
the
gal
who,
who
used
to
run
the
docker
captains
program.
She
had
her
husband,
had
made
a
small,
no
noise
cancelling
room
in
their
garage,
so
he
just
built
a
little
box
for
her
to
sit
in
in
the
garage
and
yeah.
She
definitely
didn't
have
anything
else
in
that
room.
It
was
a
tiny
little
like
telephone
booth.
Almost.
B
A
You
know
I
I
maybe
I
shouldn't
I
think
cush
has
seen
a
few
bit
of
things,
but
I
shouldn't
show
you
the
rest,
because
it's
well.
I
don't
know
how
to
put
it.
I
we
have.
We
have
some
nice
things
here
and
that's
because
well
frankly,
because
I've
worked
my
tail
off
over
the
last
25
years
and
and
it's
paid
off
but
but
shoot
now,
I
don't
use
half
of
it
because
I'm
because
I'm
we're
trying
to
make
this
a
thing.
A
So
I
think
I
think
we
are
making
this
a
thing
by
the
way
we
are
the
community
and
the
cadence
by
which
we're
doing
things.
The
fact
that,
like
in
the
last,
I
don't
know
the
last
like
two
months
really,
we've
had
well,
I
think,
like
literally
maybe
eight
repositories
created.
I
mean
we've
created
like
two
two
or
three
new
initiatives
over
and
beyond
the
core
measuring
which
is
which
is
fantastic
because
you
know,
as
we
move
into
stuff
like
web
assembly
or
just
you
know,
other
projects,
it's
really
good.
A
It's
it's
exciting
for
me,
and
I
know,
and
when
I
say
that
for
me
I
mean
I
really
mean
for
us.
I
hope
I've
said
it
to
you
guys
any
number
of
times
that
I,
as
a
matter
of
fact,
I'm
not
sure
that
I
shared
with
some
of
you
there's
a
a
young
lady
who's
here,
studying
here
in
the
u.s,
her
name's
ishida.
She
she's
a
really
nice
gal.
A
She
just
joined
the
community
not
too
long
ago,
just
like
a
couple
of
weeks
ago,
but
but
she's
not
new
to
the
community,
in
that
she
used
mystery
as
her
final
project
she's
doing
her
masters
of
computer
science.
Here
in
the
u.s
she's
from
india.
I
forget
where
but
is
doing
good
things
and
the
project
has
already
had
such
a
an
impact
on
her
and
what
her
focus
is.
So
it's
really
cool
the
things
that
you
guys
should
be
proud
of.
I
guess
is
what
I'm
saying.
A
A
A
A
A
A
But
it's
a
cross-cutting
group,
if
you
will,
rather
all
of
the
things
that
we
do,
need
continuous
integration
and
for
gungeon
and
syme
shreddy
is
on
her
way
through
her
undergraduate
studying
in
computer
science
in
general.
Studying
to
do
software,
engineering
and
part
of
her
early
focus
is
a
bit
of
front
front,
end
orientation
and
then
also
a
bit
of
technical
writing.
A
Both
of
those
areas
are,
we
we
desperately
need
more
capable
people
of.
So
I'm
really
pleased
that
she's
here
she's
also,
you
know
intrigued
by
and
interested
in
the
google
season
of
docs
and
and
the
initiatives
that
are
within
there,
so
so
actually
she's
jumped
in
into
a
couple
of
areas
we're
gonna.
I
think
kush
and
shreddy
are.
A
A
A
I
consider
that
it's
kind
of
like
signing
off
your
commits
it's
one
of
those
things
that
will
sort
of
always
be
a
perpetual
pain
point
unless
we
go
off
and
write
a
dco
specific
bot,
but
even
at
that,
like
people,
it's
it's
something
that
people
don't
always
understand
the
same
thing
for
the
finer
details
on
people,
just
not
necessarily
knowing
that
one
label
was
more
appropriate
than
the
next
like.
If
there
was
a
feature
label
and
an
enhancement
label
like
do
they
really
know
what
the
difference
is.
F
A
F
No,
if
you
are
talking
about
the
ci
so
for
the
ci
we
will
be,
we
will
be
considering
the
metadata
the
label
metadata.
I
am
talking
about
auto
labeling
of
pull
request
so
for
the
ci.
It
is
pretty
clear
that
once
we
have
finalized
the
labels,
we
can
go
ahead
and
finalize
like
how
we
want
to
initiate
the
ci
workflows,
but
first
we
will
need
to
figure
out
that
do
we
need
do.
F
A
A
We
should
be
using
labels
as
versus
titles,
in
a
pr
counting
on
a
human
to
consistently
use
the
same
style
and
grammar
like
whether
someone
did
ui
colon
or
square
brackets
as
the
label
or
parentheses
as
a
label,
or
they
spelled
out
user
interface
and
not
ui
or
they
put
area.
Slash
ui
like
the
labels
are
the
way
that
we
want
to
ideally
go
because
those
are
discrete,
auto
labeling
based
on
directory
change
or
changes
to
files
and
directory.
A
That's
a
much
more
clear
approach
as
well,
because,
literally,
if
those
files
have
changed
inside
of
a
javascript
centric
directory,
they
probably
need
javascript
changes.
If
that
logic
gets
it
wrong,
occasionally
it's
not
the
end
of
the
world
if
the
the
way
that
it
would
be
if
the
build
did
too
much
building,
it
would
just
take
longer
than
you
would
ideally
like,
but
it
wouldn't
be
the
end
of
the
world
where
the
issue
comes
in
is,
if
you
have
ui
changes,
for
example,
but
didn't
carry
that
label
and
instead
some
go
was
built.
A
A
Pr
titles
we
do
want
to
train
people
to
do
both
like
for
the
triager
and
for
anyone
trying
to
look
up
an
issue.
It's
nice
when
there's
consistency
in
the
formatting
of
the
pr
title
or
the
issue
title.
That's
that's
nice,
it's
good!
We
should
do
it,
but
of
the
things
that
we
programmatically
flag
or
of
the
things
in
which
the
the
triage
bots
go
through
and
do
things
those
bots
are
going
to
be.
Manipulating
labels
they're
not
going
to
be
manipulating
we're
not
successfully
manipulating
the
pr
title.
A
F
No
actually,
the
directory
based
labeling
is
is,
is
more
better
than
is
better
than
the
pr
title.
Labeling
like
we
can
segregate.
First
on
the
basis
of
files
like
if
our
js
file
is
changed,
apply
a
label
ui
the
only
the
only
issue
we'll
be
hearing.
Having
is
when
a
go
link
file
is
changed
so
for
the
rolling
files
we
can
even
segregate
directories,
but
ultimately
we
will
be
reviewing
the
pr.
So
we
can
definitely
change
and
look
out
for
the
labels
like
if
they
are
wrong
or
right.
A
Perspective
think
about
it
a
little
bit
if
you
would.
The
link
to
that
document
is
right
here,
maybe
maybe
take
some
time
to
sort
of
digest.
What's
going
on,
if
you're
looking
to
digest
it
in
context
of
the
broader
picture
of
of
all
of
that
we're
doing
in
building
and
releasing
it
would
be
that
you'd
want
to
spend
time
inside
this
dock
and
kush.
We
might
have
described
part
of
this
inside
of
the
build
and
release
strategy.
Dock
I'm
not
if
we
haven't.
A
A
Sure
nice,
it's
it's
coming
along
very
well,
though,
because
we're
about
to
the
stage
where
we're
gonna
reap
what
we've
sown
in
terms
of
the
work
and
you're
right
I
pushed
like
over
the
weekend.
I
sat.
I
think
it
was
because
it
was
late
at
night
and
I
had
no
more
brain
power
left
than
to
do
a
menial
task
like
just
going
through
and
and
updating
all
the
issue.
Titles
to
have
like
ui
ci,
whatever
was
appropriate,
and
I
I
don't
it's
not
that
I
mind
doing
it.
A
I
don't,
but
ideally
where
we
get
to
a
situation
where
it's
more
aesthetic
than
it
is
anything
else
and
the
reality
is
like.
If
I
really
do
want
to
find
all
the
ui
issue
related
things,
I
really
should
just
click
the
label
and
then
because
you
know
I
can't
I'm
not
going
to
be
able
to
it's
a
bit
more
tough.
To
sort
of.
A
G
A
A
F
C
A
Yep
and
what
is
the
format
that,
where
is
the
form
the
format?
Is
I
see
you're
saying:
hey,
look:
we've
gotten
some
automation
going
that
automation
is
whenever
a
pr
is
merged
in
the
measuring
repo,
and
maybe
the
other
repos
we're
using
release
drafter
to
keep
track
of
some
notes.
But
the
notes
are
just
in
they're,
not
in
markdown
format.
A
A
A
A
A
H
H
F
A
A
A
A
A
G
G
A
E
H
F
A
E
A
D
A
H
H
A
Yeah,
no,
I
don't
know,
I
don't
know
just
just
never
mind,
never
mind
I'll,
explain
later
so
guys.
I
guess
to
wrap
this
up
very
quickly,
I'm
in
favor
of
what
I'm
in
favor
of
two
things,
one
hey,
let's
just
dismiss
the
issue
say
we
would
like
to
have
the
check
boxes
right
now.
We've
got
more
important
things
to
do.
Let's
figure
out
something
later
or
we
could
say,
hey,
look
it.
H
A
A
A
I
would
say
that,
like
hey,
it
doesn't
hurt
anything
I
mean
if
you
were
to
do
what
was
suggested.
You
know
fork
slack
and
extended
put
into
the
two
forums.
Take
a
quick
peek
at
how
you
can
interface
with
mailchimp
to
just
sign.
You
know,
programmatically
sign
someone
up
and
then
that's
it
like.
If
you
get
the
whole
thing
working,
we
just
swap
it
in
and
leave
it
for.
However,
long
slack
supports
legacy
tokens
and
at
that
point
we're
gonna
have
to
deal
with
it.