►
From YouTube: Office Hours: 2021-07-15
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
So
in
order
to
automate
that
entire
process,
we
build
a
github
action,
and
now
let
me
show
the
recording
and
through
that
recording
it
could
be
clear
how
that
how
this
works
and
how
this
application,
how
this
workflow
now
works,
and
we
are
almost
done
with
our
gsoc
20
2021
project
that
we
had
in
our
agenda
few
things
more
low
level
tasks
are
lined
up,
but
that
would
be
eventually
happening.
So
let
me
share
the
screen.
B
All
right,
just
before
you
start,
I
wanted
to
ask
yeah.
Yes,
this
is
some
github
actions
for
the
build
pack
registry.
Are
we
I'm
not
super
involved
in
registry
stuff?
I
just
wanted
later
right
audience.
Yeah.
A
Yeah
yeah,
let
let
me
explain
the
project
is
small.
So
what
happens
that
whenever
we
have
this
repository,
build
packs,
github
actions
whenever
we
release
it
on
release?
If
we
observe
our
registry
index
repository,
the
workflow
is
there
use
github
actions,
version
version
semantics
so
like
right
now,
if
if
earlier,
the
version
was
4.2.0,
so
after
we
release
this
new
version,
it
has
to
be
updated
there
as
well
in
registry
index
as
well.
So
now
this
process
so
earlier.
What
happened?
A
What
used
to
happen
that
we
we
used
to
manually,
create
the
pr
we
used
to
manually,
update
the
commit
we
we
used
to
manually
create
a
commit
that
that
that
has
to
update
the
version
in
registry
index,
but
now
this
workflow
whatever.
A
What
will
happen
is
that
whenever
we
trigger
a
release
in
github
actions
repository,
it
will
create
a
repository
dispatch
event
hook
and
that
event
will
be
accepted
by
buildtax
registry
index
as
a
trigger,
and
that
will
create
a
full
request
in
registry
index
repository
against
its
workflow
file,
which
will
update
the
version
there.
So,
as
we
see
like
right
now
here,
I'm
playing
the
video
right
now
like
we
published
the
release.
This
is
this
has
happened
on
the
official
depository
we
published
the
release
and
after
publishing
the
release.
A
Now
we
will
see
this
whether
this
action
is
working
or
not.
So
we
will
go
to
first
of
all
see
if
it
has
been
released
so
it's
released,
then
we
will
go
to
actions
within
github
actions,
so
as
we
as
we
can
see
as
we
go
down
as
we
go
down
that
hook
that
we
created
that
was,
my
project
is
working.
It
shows
a
green
sign.
A
So
now
we
go
to
registry
index
repository
and
we
see
here
that
whether
the
release
event
has
triggered
or
not-
and
yes,
it
has
triggered
and
it
is
working
and
after
this
event,
this
action
is
successful.
We
will
see
that
the
pull
request
has
been
created.
Now
this
pull
request.
What
does
what
does
this
pro
liquid?
Does
this
pull
request
changes
the
version
4.2.0
to
4.2.2
automatically,
so
entire
process
is
automated
now.
So
this
was
my
project
for
google
summer
of
code,
and
this
is
how
it
was
built.
A
So
this
this
pull
request
had
a
small
problem
that
the
commit
was
not
signed
off.
So
I
fixed
that
as
well
and
now
the
merged
pr
lies
here.
I'm
sharing
the
link
to
that
pr.
So
this
was
this
was
the
final
pull
request
that
was
merged
by
joe,
so
that
that
was
the
project
how
it
works.
I
I
hope
I
I
have
been
able
to
explain
some
part
of
it.
B
C
B
B
Awesome,
unless
there's
anything
else
on
that
next
briefing
about
progress
on
solving
this
pack
issue.
C
Yeah
it's
me
and
before
I
start
about
my
progress,
I
would
say
that
I'm
really
very
thankful
to
javier.
I
have
been
having
a
very
rough
month.
I
would
say
from
june
I
went
a
surgery
of
my
gallbladder
and
then
I
had
my
graduation
or
let's
say
my
like.
I
just
ended
my
university
exam
today,
so
I'm
officially
unofficially
graduated
and
then
there
has
been
some
deaths
in
my
family
as
well.
So
it
has
been
a
very
rough
time
and
then
also.
C
This
is
my
first
time
that
I
am
participating
in
an
open
source
program
and
I
think
the
very
immediate
kickstart
was
given
to
me
by
xavier
and
we
did
fair
programming
and
we
tried
solving
the
issue
and
I'm
working
on
the
issue
where
we
are
embedding
source
metadata
in
the
oci
image.
So
there
are
three
issues
under
it
and
the
first
one
is
where
we
are
providing
project
source
metadata
from
the
the
projector
2ml
file,
and
then
I
spent
my
initial
days
on
researching
how
to
get
along
things.
C
The
first
comment
that
that
is
where
I
passed
the
file
and
then
I
also
made
the
project
military
2m
file
and
made
a
pr
that
is
my
first
pr
to
the
project,
but
sadly
that
failed
only
five,
I
think
github
actions
have
successfully
run
the
others
were
did
not,
and
then
I
also
received
some
comments
from
anthony
and
even
he
has
told
that
he
would
love
to
help,
and
I
think
that
I'm
also
researching
on
the
third
issue
and
for
the
second
issue,
I
think
I
can
use
some
verbs
help
as
well.
C
I
have
seen
his
comments
so
yeah,
that's
it
about
me
and
I'm
very
excited
because
I'm
working
on
a
project
that
is
completely
new
and
I'm
also
learning
go
for
the
first
time
so
yeah,
I'm
loving
the
experience
and-
and
I
would
again
before
ending,
I
would
love
to
mention
about
jbl's
contribution,
because
without
him
I
was
very
miserable
and
I
like,
I
always
thought
that
I
would.
I
will
start
with
the
project,
but
then
I
thought,
okay,
I'm
not
getting
well.
Things
are
not
going
fine
with
me,
then.