►
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
Is
jared
kostrowski?
I
am
a
product
designer
on
the
foundations
team
and
I'm
going
to
be
going
through
authoring,
a
pipeline
for
a
ux
scorecard
with
nadia,
and
so
I'm
just
going
to
read
this
through
and
we're
going
to
go
and
try
and
author
pipeline,
so
the
jobs
to
be
done
is
once
I
have
a
stable
development
or
operations
organization.
I
want
to
author
a
ci
pipeline,
so
others
in
my
team
can
leverage
ci
to
increase
the
efficiency
of
their
tasks.
A
So
we
have
a
team.
We
have
developers
and
now
I'm
gonna
author,
some
ci
pipelines,
so
that
our
code
adheres
to
how
we
want
to
structure
it
and
go
through
some
various
checks.
And
so
the
scenario
here
is
that
I'm
a
developer
and
my
company
is
building
a
new
website.
We
even
I
was
invited
to
this
project
open
it
up.
A
A
A
Build
the
website,
I've
already
done
all
that
and
just
run
gatsby
build.
A
A
Okay,
this
is
where
I
got
confused
again.
I
was
literally
running
these
in
the
terminal.
Forgive
me
this
is
what
I'm
supposed
to
be
adding
to
the
ci
file,
so
what
I
would
do
as
a
developer
is
either
come
and
create
a
gitlab
ci
file.
A
A
Okay,
it
looks
like
we
need
to
create
a
ci
file.
A
A
A
A
Done
too
much
of
this,
what
I
would
normally
do
so
also
gillab
ci
build
commands.
A
Well,
I
see
this
is
a
command,
and
I
know
these
are
commands
that
you
can
run
in
the
command
line.
So
I
think
I'm
just
gonna
run
with
this
one,
because
it
looks
cash
cash
results
of
the
build
in
these
pads.
A
All
right
so
stage
bill
we're
just
gonna
copy
this,
because
that's
what
I
do
and
I
don't
know
how
to
do
something
so
editor
script,
just
tab
over
okay.
This
is
gonna,
be
a
new.
A
A
A
A
A
Otherwise,
if
I'm
doing
it
in
an
editor
like
vs
code
or
something
that's,
what
I'm
going
back
and
forth
between
the
docs
and
trying
to
like
mess
with
this
locally.
But
if
my
intent
immediately
is
to
go
in
and
create
a
gitlab
ci
in
git
lab
itself,
I
would
expect
it
to
be
a
user.
A
Experience
just
clicking
around
and
clicking
on
stuff
and
sort
of
like
building
but
anyways.
That's
just
an
initial
thought.
So.
A
A
A
Seeing
your
different
stages
and
then
you
like,
can
click
a
button
in
a
drop
down,
maybe
and
like
click,
your
options,
sort
of
like
a
bunch
of
check
boxes
and
then
select
the
options
that
you
want
to
roll
with
and
then
have
it
update
this.
A
I
don't
know
total
blue
sky
thinking
here,
just
going
back
and
forth
between
the
documentation,
I've
always
found
as
a
pain,
and
I
always
you
know
when
we
redid
the
empty
state
documentation
in
pajamas.
I
wanted
to
like
emphasize
that
that's
not
a
great
experience
if
you're
having
to
go
back
and
forth
between
documentation,
especially
you
know.
I
have
multiple
tabs
open
now,
because
I've
opened
in
a
new
tab
and
I'm
going
between
different
things
and
it's
hard.