►
From YouTube: CI/CD UX Team Design Review | 7 January 2020
Description
- Dimitrie Hoekstra | 00:30
Design exploration of iteratively guiding the user to setting up GitLab-CI.
- Juan J. Ramirez | 39:48
GitLab Test project for UX team to play with features and use them when designing.
A
Saoirse
awesome
so
I
think
it's
a
good
time
to
jump
and
give
the
word
to
Dimitri
to
talk
about
his
issue
and
then,
if
because
I
feel
like,
we
will
have
some
time
left.
If
anyone
wants
to
pick
up
any
other
topic
or
just
discuss
something
else,
let's
use
the
time
as
well
or
just
drop
off
our
new
Timmy
tee
yeah.
B
I,
just
I
put
this
in
here
the
word
too
many
items
yet
so
at
least
we
have
something
to
talk
about
and
I
wanted.
Your
advice,
and
you
know
for
myself
to
be
prepared,
as
best
as
possible
for
an
upcoming
may
be
later
this
week.
So
to
give
you
the
gist
of
it.
If
you
want
to
fool
Geist,
you
can
watch
the
UX
showcase
edition.
I
did
not
so
long
ago
where
I
go
over.
B
So
this
exploration,
you
know,
I'm
gonna,
id8,
prioritize,
it
subtract,
cross-functionally,
product
management
and
engineering,
and
later
this
week,
I'll
have
you
know
the
first
real
kickoff
meeting
involving
engineering.
You
know
to
get
them
aligned
to
get
a
little
bit
more
background
story
as
to
what
effort
has
gone
into
this
and,
above
all,
to
get
their
input
as
well
into
this
explorations
see
now,
how
can
we
best
set
up
the
user?
For
you
know
setting
up
good
web
science,
it's
a
North,
Star
approach.
B
For
some
reason:
I,
don't
know
what
I'm
gonna
change,
but
there
was
like
in
this
noise,
and
now
it's
gone
so
it
feels
like
my
audio
is
disconnected
that's.
None
of
you
are
speaking.
It
seems
it's
still
working
good
good
for
me
anyway.
The
first
step
that
I
did
in
this
is
create
the
storyboard
I'll
spin.
Discussing
this
with
even
see
work,
showcase
I'll
be
showing
you
around
a
little
bit.
B
So
I'll
share
my
screen
a
little
bit,
but
what
I
would
like
to
out
of
this
is
you
know
getting
some
advice
from
from
you
all
I
still,
you
know
how
you
approach
certain
similar
efforts,
and
perhaps
we
can
also
go
over
the
you
know,
setting
up
good
web
CI
flow
over
all
familiar
with
it,
and
you
know
perhaps
I've
missed
a
thing
or
two.
So
let
me
share
my
screen
and
then
we
can
go
from
there.
I.
C
A
B
All
right,
so
this
is
a
story.
Map
I
need
to
get
a
little
bit
back
into
it.
There's
been
no
Christmas
holidays
for
me
as
well,
but
basically
they're.
You
know
they're
there
for
themes.
It's
now
learning
about
the
availability
of
good
web
ci.
That's
you
know
only
a
little
bit
into
the
marketing
side
of
it,
so
less
relevant
I
would
say
to
the
experience
I'm
trying
to
to
improve,
but
still
interesting
to
at
least
list.
B
Then
we
have
the
activation
of
CI
right
like
if
the
project
didn't
start
out
at
all
certified
CI
in
order
to
get
forward,
then
it's
about
validating
that
initial
CI
configuration
or
even
evaluating
you
know,
you're,
just
the
configuration
that
brings
us,
and
you
know
back
to
the
last
point.
That's
adjustment,
which
is
I,
would
say,
along
with
validation,
the
most
frequently
exercise
part
of
setting
up
Phillip
CI.
B
So
a
big
theme
with
this
you
know
ideal
way
of
setting
up
user
for
setting
up
a
bleb
CI
is
guiding
them
along
the
way,
and
for
that
for
us
to
do
that,
we're
gonna
suggest
the
things
so
think
of
suggesting
fixes
for
existing
configuration
errors
or
perhaps
even
when
something
is
going
well.
We
can
suggest
the
user,
based
on
the
existing
project.
Configuration
hey,
perhaps
this
is
a
thing
for
you
to
do.
B
You
know
we
want
to
link
your
your
JavaScript
to
want
to
link
your
Python
file
for
new
best
practices,
but
there's
there's
a
lot
more
to
do
there,
for
example,
for
suggesting
fixes
to
existing
CIO
configuration.
We've
all
had
that.
You
know
you
go
back
to
your
pipelines
table
and
your
CI
mo
was
invalid.
Why
don't
we
offer
the
user
and
the
ability
immediately
link
that
or
go
back
to
the
landing
pasted
in
there?
B
You
know
automate
that
suggestion
or
even
create
a
merge
quest
upon
merge
quest,
which
you
know
fixes
that
we
can
do
a
lot
of
automation
there,
along
with
suggestion
you
read
the
status
noted
their
progression.
You
read
the
build
details
if
needed,
often
done
when
users
are
less
confident
and
lies
result
discuss
the
results
with
peers.
That
is
also
a
suggestion.
How
can
we,
you
know,
make
that
process
a
little
bit
easier?
B
Currently,
it's
not
possible
to
really
discuss
a
specific
job
error,
just
just
some
ideas
throwing
in
there
and
then
you
think
of
the
improvement
or
better
suggestion
again.
So
what
I
wonder
about
here
is
you
know
if
you
do
an
exploration
and
what
I'm,
what
I'm
considering
doing
is
you
know,
walk
weird
engineering
and
product
management
cross
this
flow
and
then
consider
all
the
green
items
here,
which
are
you
know,
basic
suggestions,
as
you
know,
ideas
how
to
approve
those
steps,
so
these
three
you
see
here
would
be
you
know,
suggestions
to
improve
this.
B
D
This
looks
very
similar
to
what
I
have
been
doing
with
testing.
You
know
like
kinda
like
going
through
like
that
creating
kinda
like
those
major
topics
and
then,
like
you,
know,
kind
of
had
that
affinity.
I,
don't
know
like
an
affinity,
affinity,
diagram
of
like
things
that
you
need
to
complete
to
improve
those
areas.
Saline
yeah
I
did
similar
to
what
we
have
been
doing.
It's
definitely
not
the
same,
but
I
think
it's
kind
of
like
we
also
have
our
journey
and
then
like.
We
can't
like
go
through
the
journey
of
the
feature
we
said.
D
Okay,
this
is
the
things
that
we
need
to
like
fvc
nice
to
haves
like
Mouse
hops.
You
know,
like
I,
think
so.
I
actually
like
this
approach,
a
lot
because
you're
ready
can
I
paint
the
whole
picture.
So
it's
it's
very
clear
I
mean
if
the
feedback,
the
feedback
we're
seeking
for
is
like
the.
If
is
this
good
I
really,
like
me,
I
think
they
will
definitely
use
these.
If
you
can
share,
though
temple.
B
Yeah,
the
the
link
is
in
the
document,
so
you
can
find
it
there
and
there's
a
link
to
a
similar
approach
inside
the
product
development
workflow,
which
kind
of
you
know,
outlines
storyboarding,
but
I
was
perhaps
know
an
additional
question
towards
that.
Thanks
by
the
way
I
see
you
know,
how
do
you
make
sure
you
don't
miss
anything
or
you
know
how
we
get
extra
influences
in
there.
B
D
Don't
know
it
seems
to
me
that
you
were
gonna
miss
things,
even
if
you
don't
want
to
because,
like
it's
such
complex
I
mean
this
is
a
massive
thing.
You
know
like
CGI
configuration
like
be,
like
you
know,
setting
up
your
see,
I
am
activating.
You
see,
I,
also
like
getting
the
results
from
your
CIO
that
solves
massive.
D
B
B
E
B
D
B
A
It's
great
to
be
five,
the
one
possibility
to
visit
this
board
and
we
to
to
better
understand
like
the
flaw
that
you
presented
there.
You
know
the
steps
so
yeah,
maybe
if
we
will
finish
this
meeting
like
20
minutes
or
there,
maybe
people
can
use
those
twenty
minutes
to
give
you
feedback
here
and
providing
suggestions.
A
F
F
F
Kind
of
the
visual
editor
making
the
web
ID
that
that
kind
of
column
there
all
of
that
stuff
is
what
we're
talking
about
as
needed
solutions.
So
there's
not
really
useful
to
use
and
adding
that
new
ideas
here.
So
I
can
validate
that
these
things
are
coming
up
in
other
things,
and
these
are
the
kind
of
things
that
we're
seeing
that
we
need
in
other
areas
as
well.
So
I
guess
two
points
there.
F
One
validation,
yes,
I,
think
a
lot
of
these
are
correct,
and
maybe
we
can
wait
some
of
these
as
needed
and
other
items
as
well,
but
then
also
like
I
think
we
need
to
start
kind
of
collaborating.
That's
on
our
to-do
list
that
was
out
of
that
meeting
was
we
need
to
talk
to
Demetri
and
say
what,
where
he's
at,
and
what's
his
progress
on
this,
because
there's
a
desire
and
other
stage
groups
to
touch
a
lot
of
these
areas.
F
B
Yeah
the
little
lines
low
with
with
my
thinking
of
how
to
set
this
up,
because
I
feel
that
a
lot
of
the
places
where
you
know,
for
example,
I-
wanted
to
zoom
in
where
suggestions
are
going
to
become
making
sense.
If
you
get
a
system
to
that
suggestion
for
something
new.
So
currently,
when
you
create
your
CI
configuration
right,
you
have
to
write
it
up.
You
have
some
kind
of
a
templating
solution,
but
that's
it.
It's
super
rigid
right.
B
It
doesn't
allow
the
user
to,
for
example,
add
a
little
piece
of
information
within
their
give
up.
Yet
we
don't
have
a
you
know,
a
graphical
user
interface
to
guide
the
user
throughout
the
process
of
Korean
there
CI,
apart
from
you,
know
the
raw
text,
etc
and
I
would
say,
or
what
I
would
I
expect
here.
You
know
looking
at
get
get
up
actions
being
a
good
example
there.
B
It
would
basically
allow
us
to
create
a
framework
where
we
can
all
extend
such
things
upon.
You
know:
hey,
do
you
want
to
create
pages?
We
have
this
suggestion
or
just
add
this
get
LePage's
block
and
it
will
do
the
rest
for
you.
You
would
just
need
this
little
piece
of
information
to
which
domain
it's
gonna
point
to,
and
then
you
have
to
get
a
pages
set
up
for
you.
F
Campbell
help
people
to
understand
how
to
do
this,
because
delta
T
right
now
is
digging
through
documentation
and
hoping
you
find
it
snip
in
there
and
copy
and
pasting
that
one
so
I
think
templates
and
snippets
is
a
huge
driver
here
and
it
seems
very
North,
Star
II,
but
it
does
it
right.
We
have
all
this
code,
we're
really
talking
about
like
a
searchable
widget
that
lives
next
to
the
code
editor.
B
Yeah
that
kind
of
aligns
with
my
thinking
as
well-
perhaps
it's
a
you
know
an
iterative
way
to
get
us
to
that.
You
know
GUI.
Do
we
way
of
doing
things
at
the
same
time
and
I
do
know
that
we're
having
a
new
stage
group
set
up?
That
is
going
to
look
specifically
at
CI
onboarding.
So
you
know
there
is
the
importance
that
it
is.
You
know
it's
super-important
where
you're
creating
a
separate
state
room
for
it.
B
So
this
is
perhaps
the
pre
work
being
done
for
that
space
group
and
I
think
that
the
more
we
do
here
better
day
your
set
up.
But
if
that
is
the
case,
it
means
that
you
know
the
beginning.
User
or
user
that
are
less
familiar
with
CI
from
gitlab
are
a
really
important
target
audience
where
we
should
focus
on,
and
that
hasn't
always
been
as
clear
in
the
past
where
we
are
thinking.
But
you
know,
I
got
hopes,
engineer
or
suffer
a
developer
from
a
know,
big
enterprise
customer.
B
They
should
already
have
know
some
knowledge
and
they
should
be
able
to
figure
it
out.
I
think
now
we're
in
this
position,
where
we
can
no
longer
say
that
it's
true
and
that
we're
actually
missing
customers
based
on
you,
know
competitive
product.
Who
do
you
know
better
than
us
in
terms
of
accessibility
and
those
kind
of
things
so
yeah
I
see
I,
see
why
food
with
snippets
and
temple
thing
for
sure
what
about
you,
Rayanna
I,
haven't
heard
no.
H
I'm
sorry,
I'm
I
didn't
eat
anything
today,
so
I'm
trying
to
follow
the
conversation
mostly
but
yeah
I
think
put
this
with
the
snippets
and
the
helpers
in
the
UI.
We
also
have
the
discussions
with
Twitter,
Jackie
or
p.m.
for
release.
If
you
made
a
good
point
that,
although
we
want
to
make
things
easier,
you
want
to
automate
as
much
as
we
can
there's
also
a
lot
of
the
customers
right
that
we
they
still
want
to
manually,
perform
these
actions
like
I,
don't
know
Lerman
agencies,
banks,
etc.
H
B
Agree
there,
how,
though,
how
I
think
about
it?
But
correct
me
if
I'm
wrong
is
that
you
know
you
can
have
if
you
set
up
a
web
application
right,
you
have
your
API
and
you
build
one
interface
upon
it
that
uses
that
API
to
control
it.
But
you
can
then
also,
at
the
same
time
build
a
second
UI
that
uses
that
same
API
in
a
different
way.
B
To
get
to
the
same
result,
so
I
would
say
that
the
GUI
shoot
in
some
way
have
the
gitlab
CI
animal
as
its
API
to
get
the
same
things
done
and
but
at
the
same
time
not
have
three
works.
As
an
example,
there
it's
what's
called
DreamWorks
right
that
all
applications
from
Adobe
that
you
could
write
web
applications
with
or
something
like
that,
but
produce
bad
code.
D
All
right,
I'll
stop
sharing
my
screen
by
the
way
oh
I
was
playing
weed
these
last
week.
A
lot
yeah
I
think
the
most
frustrating
part
for
me
was
like
generating
errors
on
the
configuration
and
then
like
there's
kind
of
like
there's
like
something
that
tells
you
like.
Oh
you
have
an
error
right.
You
have
absolutely
no
idea.
D
What's
the
error,
you
know
like
I,
think
that
was
the
most
frustrating
part
because,
like
I
mean
I'm
just
saying
these,
because
I
I
was
seeing
about
all
the
things
they
were
going
through
and
I
was
singing.
What
was
the
most
frustrating
thing?
One
thing
that
it
ain't
really
be
like
a
an
area
focus
was
like
working
on
the
on
the
Yama
file,
getting
errors
and
don't
even
normally
how
to
fix
them.
It
was
like
the
error
is
not
useful.
You
know,
you
know
it's
like.
Oh,
you
have
an
error.
D
D
So
I
don't
know,
I
feel
that
if
I
was
frustrated
with
that
and
I
was
like
being
like
seen
it
through
the
eyes
of
gitlab
kidnap,
employee
I
can
imagine
like
sometimes
people
who
are
like
just
getting
started
with
these.
They
feel
about
it.
You
know
so
my
my
two
cents
are
like
if
I
was
gonna
focus
on
something,
is
it
that
particular
moment
in
which
you're
creating
the
Yama
file
I?
D
F
One
thing
I
do
see
missing
from
this
is
I,
don't
really
know
how
to
reword
it
as
a
story
map,
but
it's
you
were
hitting
on
a
little
bit
with
the
with
the
Dream
Weaver
thing
is
the
conversation
always
comes
up
of.
Are
we
gonna
put
that
as
an
option
that
you
set
in
the
yellow
file,
or
is
that
gonna
go
in
the
UI?
F
So
that's
there's
always
that
debate
back
and
forth.
So
maybe
the
story,
not
part
of
it
is
a
user
now
has
to
remember,
like
do
I
set
this
in
the
yellow
file
or
do
I
set
this
in
the
UI.
So
something
about
determining
you
know
where,
where
this
thing
is
set,
because
there's
there's
some
things,
you
know
and
that's
a
constant
moving
barometer
of
making
those
decisions.
I
feel
like
every
time
it
comes
up.
F
B
F
I
think
that's
the
ideal
state
right
I
mean
they're.
Always
there
will
always
be
coders
that
want
to
code,
and
there
will
always
be
the
rest
of
the
planet
that
once
a
UI
and
clicking
buttons
and
making
it
easy
until
we
can
reconcile
that
somehow
will
always
be
upsetting.
You
know:
X
percentage
of
people.
F
D
I
thought
about
these
and
I,
don't
think,
there's
I,
don't
think
those
concepts
are
like
separate
to
be
honest
because,
like
if
you
have
a
UI
for
your
building
your
configuration,
then
real
time
it
should
be
building
a
file
right,
so
you
should
be
able
to
switch
it
back
and
forth.
You
know
like
like
this
will
be
able
whatever
the
UI
is
doing,
it
should
be
able
to
be
waiting
from
an
actual
file.
You
know,
I,
don't
think
that
makes
sense.
Yeah.
D
G
F
D
But
no
I
understand
what
you're
saying
it's:
it's
mostly
like.
Whatever
we
do,
it
should
be
like
good
for
both
personas
for
lack
of
a
better
term
like
if
you
want
to
like
work
on
a
GUI.
You
should
be
able
to
do
it.
You
want
to
work
on
code,
you
should
be
able
to
do
it
and
it
should
be
as
easy
both
occasionally
you
know
right
and.
F
There
are
paradigm
for
this.
You
know
there.
The
world
has
gone
to
a
markdown,
editing
world
and
that's
the
sense
that
we're
talking
about
yeah
markdown
it
or
not,
not
that
far
apart
and
there
are
gooeys
for
markdown
and
context
switching
between
the
two
work.
So
it
seems
like
we
could
make
it
work
there.
Yeah.
D
F
E
B
I'm
unsure
what
exactly
I
know
we
said
it
quite
clearly,
but
if
you're
pointing
into
the
direction
of
like
has
there
been,
you
know,
done
extensive
research
in
the
need
for
a
GUI
interface
to
edit
give
up
Seattle
there
hasn't
been
done
so
and
and
I
would
wonder
like
how
would
you
figure
out?
There
is
no
specific
need
for
such
a
thing
if
it
does
not
exist
yet
I
know
like
this
is
because
only
there's
a
competitor
has
it
word.
B
A
E
A
D
Three
or
four
issues
that
suggest
like
a
visual
editor
or
like
an
interactive
editor
and
there's
one
that
is
to
prolong
like
it,
has
like
a
lot
of
comments
and
screenshots
from
people
and
people
say
you
should
do
it
this
way
and
then
they
put
like
Dimitri
also
has
like
commented
in
bow
on
anything
yeah.
The.
B
A
It's
interesting
it
may
be.
Maybe
we
can
collect
those
issues
in
one
and
just
like
do
a
debrief
there.
It's
interesting.
You
know
if
that's
like,
for
example,
four
out
of
hundred
users-
or
maybe
there
are
more
you
know
like
so
basically
does
that
do
we
even
need
to
invest
time
in
trees
and
talking
about
that
or
investigating?
Is
this
something
important
for
business
to
do
or
not?
So
all
of
those
questions
are
really
interesting
because
I
sound
Zack
we're
discussing
this
already.
D
Oh
there's
another
thing:
I
just
remember:
when
github
loud
actions,
there
was
a
threading
in
park,
earnings
and
I
remember
seeing
comments
there
that
were,
like
oh
I,
hope,
I.
My
wish
kidnap
hobbies.
This
is
pretty
cool.
I
wish.
There
was
like
a
way
like
a
UI
to
build
pipelines,
blah
blah
blah.
So
maybe
we
should
just
find
that
as
another
kind
of
like
data
plan
I,
remember
seeing
a
lot
of.
B
Good
point:
I
always
funded
them
a
little
bit.
You
know
strange
to
be
able
to
gather
such
different
qualitative
sources
and
then
just
you
know,
pile
them
together
as
a
piece
of
evidence
for
the
need
for
something
like.
Is
there
a
better
way
to
perhaps
compare
the
results
from
those
different
kind
of
sources?
And
you
know
hey
this
thing
points
into
this.
You
know
percentage
of
need.
I
know
this
is
pretty
very
good.
B
C
D
Point
out
something
else:
it's
related
perhaps
like
it's
another
need,
but
when
I
was
playing
with
these
last
week,
I
think
one
thing
that
really
frustrate
straighten
me
was
the
fact
that
I
was
writing
the
llamó
and
it
couldn't
preview
how
the
pipeline
is
going
to
look.
You
know
so
I
only
know
how
the
pipeline
is,
gonna,
look
until
I,
save
it
and
I
try
to
run
it
and
then
I
see
all
actually.
This
stage
is
here:
actually
the
jobs
are
running
under
this
stage.
D
You
know,
although
I
can't
like
I'm
trying
to
like
build
that
pipeline
in
my
head,
I
never
get
like
a
visual
picture
of
how
the
pipeline
looks
until
I
run.
It
and
I
think
it
ties
back
to
these.
You
know
like
I
was
trying
to
like
build
it
mentally
and
I
never
had
a
chance
to
see
how
it
looks
so
maybe
the
NBC
food
is
I,
don't
know.
Maybe
this
is
just
like
the
NBC
food
East.
It's
just
at
least
seen
like
as
we're
writing
the
llamó.
D
B
It
has
been
something
that
I
have
been
slightly
involved
with.
There
was
wondering
who
it
was,
but
there
were
two
developers
that
were
working
on
approved
concept
that
eventually
turned
out
to
be
too
difficult
to
really
pull
off
for
exactly
thing.
So
there
is
the
need
with
developers
to
you
know,
make
it
easier
and
get
feedback
earlier
on
their
CI
configuration
while
editing.
Yes,
I
truly
think
there
is
an
you
know
an
opportunity
there.
At
the
same
time,
you
know
open
kind
of
worms
like
alright,
let's
figure
this
out
as
well.
B
D
I'm
pretty
sure
it's
not
easy,
but
I
think
the
reason
was
frustrating
is
because
I
was
writing
his
channel
and
then
I
was
like
okay
piece
job
them
re.
It's
gonna
run
in
the
context
of
this
pipeline
and
then
I
run
it
and
then
I
see
that,
like
actually
it's
like
running
be
touched
and
I,
don't
know
why
you
know
and
there's
like
no
feedback
or
there's
no
trace,
there's
nothing.
That
tells
me
why
this
particular
job
that
I
think
that
running
under
a
stage
is
running
attached.
A
B
Would
be
nice
to
be
honest
if
anybody
have
done
to
store
everything
before
and
they
have
an
example
of
how
they
went
from
the
initial
story
map
towards
figuring
out
what
the
first
MVC
is,
and
you
know
how
they
prioritize
different
parts
of
the
story
map
to
be.
You
know
ideated
upon
first.
That
would
be
welcome
thing
to
look
into
or
have
an
example.
A
A
D
D
Okay,
so
last
week,
I
was
working
on
like
kind
of
like
coming
up
with
like
an
initial
person
like
like
our
CI
CD
testing
project.
So
basically,
as
you
guys
know
like,
we
usually
need
to
go
on
tests.
The
ICD
functionality
like
see
how
things
work
I,
like
it's
fine
to
our
projects
that
do
what
what
we
are
trying
to
test
so
I'm
trying
to
come
up
with
like
that
configuration
and
everything.
D
So
it's
still
very
rough,
but
my
goal
is
to
basically
build
something
that
everyone
and
these
on
this
group
news
station,
can
use
and
like
anyone
who
needs
family
trigger
a
particular,
you
know
a
particular
testing
case.
They
can
do
it
like
to
this
project
right
so
right
now,
it's
like
very
simple
right
now,
like
did
the
way
that
it
works.
Is
that
you
just
click
here
and
then
you,
you
change
this
file
to
something
else.
You
know
and
then
you
commit
when
you
come
in,
then
you
staged
that
and.
D
A
Is
amazing,
amazing,
Quan?
Thank
so
much
for
doing
that
two
comments.
Maybe
you
can
address
to
the
CI
CD
design
review
document
they
stink
so
wicked.
This
we
don't
forget
to
add
our
ideas
and
also
curious
if
you
maybe
have
recorded
how
you
did
set
this
up
or
like
curious,
if
you
would
be
able
to
to.
A
D
A
D
D
Let
me
think
of
all
you
need
to
run
like
a
detached
pipeline,
for
instance
right.
So
you
write
like
I,
already
have
like
something
working
for
this,
but,
like
my
idea,
is
that
anything
that
you
write
here
like
we
can
have
keywords,
so
you
can
say
like
oh
Multi
pipeline
or
like
detach
or
like
fail
the
pipeline.
You
know
anything
just
have
like
some
keywords
here
that
you
put
on
the
title,
the
mr
and
then
the
pipeline
is
gonna.
D
Do
whatever
you
are
asking
the
pipeline
to
do
so,
I'll
show
me
a
failed
pipeline
and
then
the
pipeline
will
fail,
and
it
really
tells
these
last
week
a
little
bit.
I
mean
I
know
how
to
do
it
and
it
works
decently.
Well,
so
that's
basically
what
I
want
to
get
to
you
know
like.
Basically
we
can
create
the
repo
here
and
then
we
can
have
like
a
list
of
all
the
ways
that
you
can
trigger
the
pipeline
in
different
ways
like
the
the
CI
in
different
ways.
You
know
do.
B
You
do
you
know
about
the
existing
project
of
get
live
examples
where
they
kind
of
try
this.
The
problem
with
having
it
within
one
project
is
that
you
know
certain
C
see
these
settings,
which
are
project.
You
know,
complete
project
settings
will
influence
the
way.
Certainly
pipelines
are
going
to
be
shown
right.
You
know
if
it's
going
to
be
a
certain
large
strategy
or
something
like
that
or
certain
approvers
are
going
to
be
active
versus
nod
or
you
know,
all
these
kind
of
things
will
have
an
effect
so
I.
My
first
thoughts
towards
this
is.
D
I
think
we
can
do
that
too.
I
mean
like.
I
think,
that
the
idea
of
this
project,
like
projects
is
to
have
a
place
where
we're
testing
things
are
specific
to
us
right
like
sometimes,
I
have
a
need
to
see
like
testing
like
failed,
a
test.
You
know
like
failed
tests
in
a
project
right,
and
it
takes
me
like
literally
like
20
minutes,
to
find
like
something
that
has
like
a
fail
particular
test
or
like
a
code-
climate
degradation,
for
instance.
D
That's
one
that
I
always
need
to
check
out
and
I
never
find
you
know
like
when
they,
when
the
code
coverage
goes
down
and
there's
a
rapport
about
that,
I
always
try
to
find
reports
in
March
that
in
which
that
happen
and
I
never
find
any
of
those.
So
I
think
the
idea
here
is
to
like
these
are
very
specific
to
our
stage.
Right
things
are
like:
oh
I
want
to
see
degraded
coverage.
I
wanna,
see
you
know,
like
children,
pipelines,
I
wanna
see
any
any
of
those
things
I
like.
D
Then
we
can
explore
to
see
if
it's
possible
within
the
context
of
these
or
we
can
create
more
projects.
Of
course,
this
is
just
start,
but
I
think
like
if
we
can
brainstorm
a
little
bit
just
by
adding
issues
to
this
project
like
oh,
you
should
try
these.
We
should
try
that
then
we
can
like
as
a
team,
we
can
explore
how
to
do
that.