►
From YouTube: Working on Global Actions Support - Part 1
Description
It's a github action that picks changes to a workflow from a given repo and populates the change to other repositories and the same workflows
A
I
think
we
were
pretty
clear
during
the
oktoberfest
that
we
would
like
to
do
those
streams
more
often,
and
today
it's
a
good
opportunity
to
do
it.
As
you
can
see,
I'm
already
sharing
my
screen,
but
before
I
jump
into
the
explanation,
let
me
just
double
check
how
the
things
work
on
youtube.
So
I
so
I'm
sure
that
you
get
a
good
quality,
so
uno
momento
per.
A
A
A
A
Or
is
it
ih
damn
it
forgot
about
forgot
about
delay,
sorry,
so
this
one
is
good
and
let's
make
this
one
bigger.
A
B
A
A
Okay,
so
last
point:
let
me
on
our
asking
api
slack,
let
me
write
in
the
tooling
section
that
I'm
live.
If
someone
wants
to
join.
A
B
A
It's
so
good
to
have
a
headphones
without
mic.
So
when
I
do
this,
I
don't
hit
the
mic.
A
Okay,
so
let
me
first
introduce
what's
the
stream
for
so
the
stream
is
not
particularly
about
the
asking
api
spec,
it's
related
to
using
api,
and
let
me
explain
to
you
so
if
you
don't
know
yet
so
in
in
asking
api
on
github
we're
using
github
actions
to
automate
all
the
things
and
we
really
automate
a
lot
of
things
with
with
github
actions
and
just
recently
we
started
getting
issues
with
with
one
action,
and
let
me
show
you
the
example.
B
A
Parser,
so
we
we
have
a
github
action
that
is
welcoming
people
the
first
time
contributors.
A
A
A
A
Here
and
let
me
show
yes,
okay
and,
as
you
can
see,
the
welcome
github
action
failed
and
it's
failing
for
at
least
two
weeks
now
for
everyone.
A
Even
if
you
are
a
contributor
already,
it's
gonna
fail
and
it's
failing
because
I
mean
I
don't
wanna
go
too
much
into
details
now,
maybe
let's
I
mean
it
happens
just
so.
The
problem
about
this
action
is
that
the
the
owners
in
the
docker
image
they
provided
and
brands
on
the
github
action.
A
Okay,
no
momento
guys
ask
me
for
a
link
to
the.
A
Stream,
thank
you
unto
neth.
A
Hey
man
thanks
for
joining
so
going
back,
oh
yeah,
so
the
the
action
started
failing
two
weeks
ago
or
three
weeks
ago,
even
and
it
was
because
the
the
owners
in
the
docker
image
that
they
provided,
they
did
not
fix
the
base
image
to
a
specific
version
of
node.js.
As
far
as
I
remember,
and
because
of
this
they
actually
started
failing.
A
I
think,
because
of
some
specific
note
version
and
the
only
possible
fix
was
to
to
yeah
fix
the
version
and
then
release
a
new
version
of
the
of
the
workflow,
which
basically
means
that
what
we
have
to
do
now.
A
To
solve
it
for
all
the
repositories
and
we
have
over
30
repositories,
we
would
have
to
go
manually
to
each
repo
to
the
workflows
directory,
get
welcome
first
time,
contributor
file
and
basically
change
this
to
latest
version,
and
basically
we
should
change
to
just
v1.
A
A
So
basically,
what
this
means
is
that
github
action
will
download
clone
this
repository
from
this
organization
from
this
stack
from
this
release.
A
Because
of
this,
you
don't
have
this
handy
notation,
I'm
not
sure.
What's
the
name
syntax,
that
in
node.js
in
package.json
you,
you
know
that
you're
doing
this,
you
can
say
that
you
you're
fixed
not
to
specific
version
but
to
to
major,
and
you
automatically
update,
always
the
the
minor
and
patch
and
it's
not
the
thing.
A
It's
not
possible
with
with
github.
So
what
they
came
up
with
is
a
recommendation
to
always
whenever
you
release
first
version
of
the
action
and
you
bump
from
one
zero
zero
to
one
zero
one.
At
the
same
time,
you
should
always
release
also
tag
v1.
A
So
if
you
for
example,
then
one
zero
one,
two
one
zero
three
or
one
one
zero.
Then
people
don't
have
to
edit
their
workflows
again,
because
your
next
version
that
starts
with
one,
you
will
also
update
the
tag.
The
v1
tag
with
the
latest
change.
A
So
because
we
assume
that
miners
and
patches
don't
introduce
breaking
changes,
so
people
can
fix
the
version
they
follow
to
v1
and
that
this
way
they
don't
have
to
update,
especially
if
we
have
bug
fixes
like
with
the
welcome
action.
A
So
I'm
gonna
just
show
a
message
from
dan
and
in
the
meantime,
I'm
gonna
ask
my
kids
to
stop
jumping
from
the
bed
on
the
floor,
because
it's
pretty
loud
at
least
I
can
hear
it.
So
you
probably
can
hear
it
as
well.
No.
A
A
Okay,
so
we
basically
have
to
fix
this
tiny
string
in
30
different
repositories,
and
you
can
imagine
like
cloning,
creating
branch
creating
prequels,
then
taking
a
review
like
damn
it.
That's
why
we're
it's?
The
action
is
still
failing
for
last
three
weeks,
because
it's
not
fun
to
update
it
and
until
yesterday,
when,
when
I
had
a
brain,
fart
came
up
with
with
this
issue,
so
I
mean
I
thought
about
it
a
while
and
it
looks
like
it's
possible.
A
So
let
me
introduce
you.
What
is
the
idea
and
what
I
want
to
do
so
I
basically
want
to
create
wait.
One
thing
more:
you
should
you
should
know
as
well
so
dot
github
repository.
A
I
think
it's
pretty
useful
knowledge
in
general.
So
github
has
this.
I
think
it's
quite
secret
feature
because
I
I've
never
heard
about
it.
It
was
introduced,
I
think
this
year
and
it's
pretty
nifty.
So
it's
a
it's
like
a
a
global
repository
for
your
for
your
organization.
A
So
if,
for
example,
you
have
you
want
to
have
issues
templates
and
you
want
to
have
those
the
same
templates
across
all
the
repositories,
then,
instead
of
creating
those
templates
in
every
repository.
A
A
You
can
create
it
here
in
this
repo
that
is
called
github.
You
just
put
issue
template
and
then
those
issue
templates
are
populated
to
all
the
other
repositories.
They
are
not
recreated,
so
they
do
not
exist
in
the
in
the
other,
verbose
they're,
just
somehow
dynamically
included,
which
is
pretty
nifty,
and
it's
amazing
solution.
We
use
it
a
lot
in
using
api
now,
but
it's
at
this
point.
It
does
not
support
global
global
actions.
A
So
what
I
mean
by
global
action
like
like
this
workflow
right,
this
workflow
is
literally
the
same.
This
file
is
exactly
the
same
in
30,
something
repositories,
so
I
mean
each
time
you
create
the
same
file
in
every
repo.
You
have
this
feeling
like
you're
doing
the
same
thing
all
over
again,
you'd
like
to
do
it
just
once
like
with
issue
templates
so
some
time
ago,.
A
A
D
D
D
A
A
Global
actions,
good
name
right
and
I
decided
to
do
it
because,
when
I
started
thinking
about
how
we
can
solve
it,
I
think
it's.
The
time
spent
on
the
action
is
similar
to
the
time
I
would
spend.
E
C
A
A
A
But
at
the
beginning
it
was,
it
was
good
right
it
just
the
the
sound
got
bad
over
time
right.
A
Okay,
I'm
not
using
obs,
I'm
using
streamy
art,
so
I
can
stream
to
youtube
twitter
and
and
twitch.
At
the
same
time,.
A
B
E
A
A
A
So
let
me
just
focus
on
that
first,
so
the
idea
here
is
that
we
treat
dot
github
repository
as
as
global
full
act
for
actions
as
well,
especially
because
it
already
has
the
same
actions
as
as
the
other
as
the
other.
A
A
Triggered
on
push
event,
because
that's
the
once
we
merge
for
request
it's
a
push
to
master
and
there's
an
event
emitted
on
github
and
because
my
workflow
is
registered
to
be
triggered
by
this
event,
then
my
actions
started
and
then
what
happens?
There
will
be
a
configuration,
so
the
action
will
have
in
the
action.
You
will
be
able
to
provide
a
list
of
workflows
that
you
want
to
be
replicated
in
in
different
repositories.
A
So,
for
example,
this
welcome
first
time
contribution
the
amp
file.
The
path
to
this
yam
file
is
gonna
be
mentioned
in
the
configuration,
if
not
mentioned,
then
by
default.
The
action
will
pick
up
all
the
files.
A
And
we
check
the
configuration
provided
by
users,
so
we
check
and
that's
what
I
want
to
have
in
the
action.
So
in
the
action.
The
user
can
provide
a
list
of
repositories
where
the
action
should
be
populated
replicated.
A
So
basically
the
file
should
be
replicated.
So
you
have
a
let's
say:
you
have
a
organization
that
has
10
repos,
but
you
need
those
workflows
only
in
five
repos,
then
you
can
specify
the
names
of
the
repositories
as
a
list
in
the
action.
A
Okay
and
then,
if
not
not
provided,
then
we
basically
assume
that
we
should
replicate
the
action
in
all
the
repos
from
a
given
organization,
and
then
we
have
to,
of
course
using
the
github
api
get
the
list
of
all
those
repos.
A
A
And
user
of
such
a
workflow
then
can
decide.
What's
next
I
mean:
should
those
prs
be
manually
reviewed
before
they
are
merged,
sure
you
can
do
it,
but
we
don't
want
to
do
it
for
30
repos.
So
we
for
sure,
as
users
of
global
actions
support,
we
will
have
another
step
in
the
workflow.
That
is
automatically
no
wait.
It's
not
going
to
be
in
the
workflow
and
in
our
case,
in
our
case
let
me
show
it
to
you.
A
So
yeah,
that's
the
intro.
What's
the
proposed
solution.
A
Okay,
don't
yeah,
so
we
have
a
so
how
the
github
action
looks
like
you
yeah.
You
need
to
have
a
basically
start
function
that
you
run
immediately
once
the.
A
Once
the
action
is
is
triggered
and
you
need
to
have
a
certain
configurations
like
I
said,
for
example,
this
action
will
have
to
support
a
list
of
of
repos,
for
example,
where
the
action
has
to
be
replicated.
A
Details
from
the
from
the
workflow
you
pick
up
in
your
code
using
a
core
library,
official
github
action
score
library,
so
you
have
a
special
api
where
you
can
just
grab
the
input
from
the
workflow.
So,
for
example,
we're
gonna
need
a
github
token,
of
course,
because
we're
gonna
create
pull
requests.
A
A
A
A
A
B
A
A
Environment
variable
okay,
so
first
thing
we
need
to
do
is
to.
A
A
let's,
let's
see
differently
so
we'd,
say
another
official
library
github
for
github
actions.
B
A
B
A
A
A
Let
me
open
it
here:
it's
called
github
craft
ql,
explorer.
A
A
So
now,
how
do
we
know?
How
can
we
check
if,
let's
our
assumption
is.
A
That
for
now,
user
cannot
specify
what
actions
were
modified.
Okay,
what
workflows
got
modified,
so
the
assumption
is
that
any
workflow
will
be
taken
by
the
action,
because
at
the
end
those
workflows
have
to
be
in
a
specific
repository
location
in
the
repository
it's
dot,
github,
slash
workflows,
so,
let's,
let's
just
make
it,
make
it
easier,
and
now
the
we
can
access
in
the
action
we
can
access
the
we
have
access
to
the
to
the
event
that
triggered
the
the
action.
A
A
A
A
A
I'm
pretty
slow
thinker
if
the
file
name
is
includes
the
dot
github,
slash,
workflow
directory.
B
A
Okay,
so
that's
the
link
to
the
official
docs
and
yeah
async
api
dot.
Github
you're
gonna
find
it
easier
than
me.
I
guess.
A
A
A
Okay,
you
see
so
yeah
the
like
in
in
github
actions.
Oh,
let
me
make
it
bigger.
So
in
github
actions
you
have
access
to
many
different
environment
variables.
Let
me
show
it
to.
A
A
Github
github
repository
is
the
name
of
the
repo
you
have
even
information
about
the
actor.
So
that's
all
these
things
are
part
of
the
environment
variables,
which
is
pretty
nifty
so
yeah.
Let
me.
A
A
Let's
assume
I
mean
not
assume
different
word,
I
just
I
mean
I
like
docs
that
they
tell
me
what's
the
structure
that
there's
files
and
there
are
yeah
additional.
A
A
A
B
B
A
A
B
B
What
of.
A
A
A
B
A
A
A
B
E
B
A
B
A
Wait
there's
this:
I
think
they
have
this
nice
nifty
yeah.
Of
course
you
had
to
fail.
They
have
this
nifty.
I
am
so
when
you
create
new
file
in
the
ui.
It's
if
you
would
create
workflow
through
the
regular
ui,
it's
like
any
other
file,
but
if
you
create
a
workflow
from
the
action
stop
see,
you
have
a
customized
ui
with
some
suggestions.
B
B
B
A
B
B
B
B
A
And
now
uses
and
uses
what
I
mean,
how
can
I
test
a
workflow,
a
action
that
is
not
yet
completed?
It's
not
released
and
it's
not
and
it's
not
published
on
actions
marketplace.
A
A
E
A
B
B
B
A
B
A
Code,
remember
keyhole
action.
C
B
B
B
B
A
I
always
at
the
end
I
always
look
on
the
code
of
other
actions.
Then
read
the
docs,
not
sure
if
it
talks
good
about
the
dogs,
but
maybe
it's
just
something
wrong
with
me.
So,
let's.
B
A
Okay,
so
pull
request.
Action
supports
youtube,
so
you
can.
A
A
A
A
Now
but
first,
let's
also
update
the
action.
So
what
am
I
doing
here?
I'm
checking
the
so
it
was
good
at
the
beginning.
Damn
it.
A
So
I
either
grab
it
from
process
environment
variables
for
local
testing
right,
so
I
have
a
variable
already
exported
here.
That
holds
my
token,
like
my
custom
token,
and
when
I
locally
start
my
my
action
I
want
to,
I
want
to
use
the
the
locally
exported
token
and
in
the
action
what's
happening,
nothing
here,
so
it's
just
gonna
pick
it
up
from
here
and
that's
why
it
was
required.
A
A
I
don't
use
git
in
terminal
almost
never
I
mean
I
use
it
to
switch
between
branches
quickly,
synchronize,
maybe
with
remote
between
my
fork
and
with
the
upstream
but
comets.
A
B
B
B
A
B
A
A
Okay,
so
we
get
like.
I
said
it's
a
it's
a
different
event.
So
it's
not
one
comment.
It's
a
it's
a
list
of.
A
B
Information-
let's
just
it's
too
huge
and.
C
A
A
Get
more
details,
I
mean
from
the
api,
so
let's
let's
try
it
so
we
already.
A
B
E
B
A
B
B
B
B
B
E
B
A
A
A
A
B
E
B
A
B
A
Those
notes,
jesus.
B
B
B
B
B
B
B
A
Okay,
that's
why
I
couldn't
find
it
because
it's
not
supported.
B
B
E
B
B
A
A
B
B
B
B
C
C
B
E
B
B
A
C
B
B
B
B
A
C
B
A
B
A
A
A
I'm
gonna
continue
work
tomorrow.
I
don't
want
to
schedule
any
specific
time,
but
I'm
sure
I'm
gonna
do
it.
In
the
morning
around
nine
nine
ten,
like
between
nine
and
ten,
I
guess
it's
going
to
be.
9
30
a.m.
A
So
it's
8
30
utc
yeah
at
the
moment
it's
utc
plus
one.
So
if
you
want
to
continue
with
me
on
the
github
action,
yeah
join
me
tomorrow
and
thanks
for
being
with
me
today,.