►
From YouTube: CI/CD UX Review - 2023-07-27
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
B
B
So
today's
issue
is
like
today,
I'm
going
to
be
sharing
the
progress
that
we
are
making
with
the
proposal
of
pitlab
native
Secrets,
POC
and
I
want
to
kind
of
reinstate
that
it's
just
a
POC,
because
I
would
also
need
some
feedback
on
what
is
it
that
I
can
remove
from
The
Proposal,
because
we
want
to
keep
it
very
bare
minimum
feature
wise
yeah
and
going
looking
at
the
background
of
this,
how
this
has
been
evolving.
B
I
started
off
with
the
like.
After
looking
at
a
regards
research
reports,
I
started
off
with
doing
a
competitor
evaluation,
just
to
get
an
idea
about
how
the
industry
is
going
about
like
doing
things
with
their
secret
management
tools.
Then
what
are
the
standard
practices
and
based
on
every
all
of
that?
B
I
created
sketching
exercise
with
some
background
information
for
the
team
to
look
at
so
that
they
get
some
inspiration
from
around
and
they
can
still
like
exercise
their
creative
muscles
and
imagine
what
a
similar
concept
that
sits
native
to
git
love
could
look
like,
and
the
outcome
of
that
was
really
interesting.
I
think
I
should
have
it
open
here,
somewhere
yeah.
This
is
these
are
all
the
things
that
we
got
from
that
exercise
and
then
we
moved
on
to
doing
a
story.
B
Mapping
exercise
because
we
really
wanted
to
be
very
sure
about
what
is
it
that
we're
enabling
users
to
perform
using
this
particular
offering.
B
So
the
four
tasks
that
we
figured
are
key
to
this
tool
that
we
are
building
are
access
to
key
storage
which,
in
our
case,
is
not
going
to
be
like
a
separate
entity,
not
a
separate
wall,
but
something
integrated
in
gitlab,
then
storing
a
key
accessing
a
key
and,
lastly,
managing
a
key,
and
you
would
see
the
security
columns
are
still
empty
because
I
have
a
meeting
schedule
with
a
security
person
from
gitlab,
where
I
would
like
be
discussing
with
them.
B
How
we
should
go
about
thinking
about
what
security
the
person
responsible
for
security
would
be
concerned
about
when
it
comes
to
Secret
anyway.
So,
looking
at
all
the
tasks
that
are
documented
here,
I'm
going
to
be
taking
you
through
I
would
say.
This
is
not
the
first
but
second
iteration
of
design,
because
the
first
went
like
this
was
the
first
one
and
we
received
a
lot
of
feedback
from
the
team
from
outside
the
team
and
based
on
all
of
that
I
made
some
refinements.
C
A
B
All
right,
the
first
mistake
is
I,
have
missed
that
there
will
be
a
secret
it's
in
the
previous
design
yeah.
This
is
going
to
carry
over.
So
let's
start
with
this,
so
here
what
you're
seeing
is
a
project
level
secret,
page
and
yeah.
I
did
not
want
to
draw
attention
to
this,
but
this
is
definitely
not
going
to
be
what
the
navigation
that
we
are
proposing.
B
I
just
wanted
to
keep
this
separate
from
builds
because
Secrets
don't
always
relate
to
bills
and
when
I
was
presenting
it
as
a
part
of
build,
it
was
kind
of
problematic
because
it
was
miscommunicating.
That
secrets
are
something
which
are
always
associated
with
builds
so
I
wanted
to
break
away
from
that,
but
that
also
opened
up
another
challenge
for
us
that
where
would
this
go?
B
And
this
is
going
to
be
more
of
a
concern
when
we
move
to
the
MBC
stage,
because
POC
is
not
going
to
be
shipped
as
a
part
of
GitHub.
It's
something
that's
going
to
be
Standalone
so
for
now,
I
can
probably
keep
it
this
way,
but
I'll
like
still
create
an
issue,
put
all
the
evidences
and
rethink
where
this
should
be
going
yeah.
B
So
for
both
the
project
and
group
level
I
plan
to
show
like
add
a
Secrets
page
where,
which
is
going
to
be
very
similar
to
look
at
when
we
go
to
like
settings,
cicd
variables
like
what
information
the
table
has,
but
a
few
things
will
be
done
differently.
B
So,
first
of
all
for
secrets,
we
are
not
going
to
show
any
value
because
once
the
secret
is
created,
nobody
gets
to
see
the
value,
even
if
they
have
the
right
to
edit,
even
if
they
are,
if
they
own
the
secret,
if
they
wish
to
edit
it
after
that,
they'll
have
to
like
completely
let
go
of
like
override
the
previous
thing
with,
and
they
never
get
to
look
at
it
again.
B
So
on
the
secrets
page.
If
there
are
secrets
that
exist,
this
is
the
table
that
they
would
get
to
see.
If
not,
then
there's
going
to
be
an
empty
State
not
worked
on
yet
so
for
a
secret
I
kind
of
proposed.
This
and
I
also
asked
Iran
in
the
team.
B
B
Now
one
thing
that
I
still
see
Clarity
on
from
the
development
team
is
if
this
is
always
if
there
is
always
going
to
be
an
environment
Associated
like
variable,
because
maybe
that's
not
a
requirement,
so
some
Secrets
will
have
environments.
Some
will
not.
Another
critical
information
to
show
are:
when
was
the
secret
last
accessed
from
yamu
from
somewhere
else,
then
when
was
it
created,
and
when
is
the
upcoming
rotation
so
for
upcoming
rotation
or
not
yeah?
B
And
let's
say
the
day
or
May
29
might
not,
then
the
rotation
should
be
relative,
like
it
should
say
that
every
Thursday
at
this
time
the
rotation
is
going
to
happen,
because
we
don't
want
to
keep
it's
very
abstract.
It
should
be
very
clearly
communicating
when
exactly
the
rotation
is
due
and
then
looking
at
what
action
actions
we
want
to
allow.
So
the
team
came
up
with
really
good
suggestions
here,
since
this
is
native
to
gitlab.
B
We
want
to
make
it
really
smooth
for
both
developers
and
maintainers
to
be
able
to
use
these
secrets
in
their
workflow,
so
keeping
the
curl
command
handy
is
kind
of
the
extra
value
that
we
can
provide
here,
because
that's
going
to
be
unique
to
gitlab,
you
can
just
come
here
copy
the
curl
commands
and
just
go
and
use
them
in
CLI.
B
That's
one!
Then
I
have
added
a
delete
icon
here.
Yes,
but
I,
don't
think
that's
the
right
one,
because
there's
still
a
discussion
going
on
whether
we
should
allow
deleting
or
revoking
access
to
a
secret,
because
deleting
might
not
be
something.
That's
that
that
is
record.
It's
not
something!
That's
recommended
because
when
it
comes
to
Secret,
there
needs
to
be
an
audit
log.
B
Audit
log
I
have
not
added
to
this
page,
but
it's
a
part
of
the
MVC
proposal
here,
because
that's
again
a
lot
of
work,
we
don't
want
to
get
into
that
in
the
POC
stage,
but
we
we.
C
B
Sure
so
audit
log
with
secret
every
small
little
thing
that
is
being
done
with
the
secret,
is
a
compliance
and
security
issue.
It's
not
something
that
should
be
taken
lightly,
so
our
users,
they
really
want
a
visibility
into
when
the
secret
was
accessed.
Who
was
it
accessed
by?
When
was
any
changes
made
to
the
access
policy
of
the
secret
and
like
who
are
the
concern?
Individuals
who
are
taking
those
actions,
like
a
record
of
that,
because
it's
really
critical
as
a
resource.
B
There's
a
there's
also
been
a
request,
a
similar
request
for
variables,
but
compared
to
variables
the
requirement
for
a
secret
audit
log
is
more
critical
and
that's
the
reason
we
can't
just
like
allow
somebody
to
just
come
and
delete
a
secret,
because
that's
something
that
needs
to
be
recorded
somewhere.
C
B
No,
there
is
no
detailed
as
of
now
and
like,
if
I
have
forgotten,
to
add
the
edit
button
yeah
there
is
an
option
to
edit,
but
when
somebody
goes
to
edit
that
what
they
will
see
is
this
form
again
that
they
use
to
create
the
secret
just
that
the
value
is
not
going
to
be
shown
to
them.
It's
probably
going
to
be
disabled,
because
if
they
really
choose
to
edit
the
value
they'll
have
to
completely
let
go
of
the
previous
value.
B
They
cannot
go
and
make
changes
to
the
value
that
they
entered
before
that
shouldn't
be
allowed.
So
what
I'm,
expecting
that
they'll
come
to
this
page
for
is
mostly
to
fix
the
access
permission
like
who
should
have
access
to
do
what,
with
the
secret
and
not
necessarily
to
change
the
key
and
value
and
I'm
here
to
create
a
screen
for
that
like
what
editing
on
the
same
screen
would
look
like,
because
not
all
of
these
fields
would
play
A
Part
there.
B
B
Yeah,
so
this
is
the
pattern
that
I'm
thinking
of
like
replicating
for
all
of
these
here
that
really
representing
when
it
was
created
when
the
rotation
is
due
and
the
and
keeping
very
few
actions
which
are
very
critical,
not
overloading
this
area
yet,
and
then,
when
users
click
on
this
button,
here,
that's
his
new
Secret.
They
will
go
to
this
form.
B
Now
this
form
used
to
be
pretty
simple,
but
it
changed
yesterday
used
to
be,
as
in
in
my
first
iterations
I
thought.
Maybe
I
can
do
everything
in
one
just
one
single
form
and
I:
don't
have
to
split
it,
but
after
so
I
had
a
meeting
with
Marshall,
but
we
also
talked
about
this
design.
So
He
suggests
like
he
brought
up
the
disadvantages
of
showing
the
preview
on
the
same
page.
What
I'm
proposing
is,
there's
a
form
you
fill
in
on
all
the
information,
but
because
secret
is
a
critical
resource.
B
We
don't
allow
just
creating
like
creating
the
secret
just
here
like
storing
it
just
yet,
but
instead
we
want
to
give
them
the
chance
to
make
any
corrections
once
they
see
a
summary
of
all
the
choices
that
they
have
made.
So,
for
example,
they
would
be
adding
access
permission
through
here
and
there
are
a
few
things
that
would
not
be
very
clear
just
from
looking
at
these
drop
downs.
B
So
let's
say
this
is
the
permission
that
they
have
added,
that
maintenance
can
be
even
edited
in
a
particular
user
can
read
and
so
like
summarizing
all
of
their
choices
together
and
showing
them
before
letting
them
add
it
to.
The
repository
is
going
to
be
very
beneficial.
It's
also
like
a
practice
that
a
couple
other
tools
follow,
but
we
can
do
it
like
we
do
it.
B
We
would
do
it
a
little
differently
and
more
to
the
benefit
of
git
lab,
because
the
commands
that
we
can
show
here
and
the
Snippets
that
we
can
show
here
can
be
exclusive
to
the
actions
within
gitlav
like
besides
scroll
commands,
which
I
think
is
for
POC.
Maybe
in
MVC
we
can
show
them
how
this
would
be
used
in
a
yaml
file,
and
that
would
give
them
pretty
good
idea
about
what
the
secret
would
look
like
in
a
yaml
file
before
they
go
and
add
it.
B
So
once
they
are
happy
with
what
they
see
as
a
preview,
they
can
just
go
and
click
on
ADD
else.
They
can
just
go
back
and
click
on
edit
and
go
back
to
the
form
make
changes
again.
B
B
And
this
is
what
I
have
for
now
now
I
have
highlighted
some
questions
in
the
in
in
the
agenda,
the
first
one
being
if
the
user
flow
like
from
a
top
level,
if
this
makes
sense
or
are
there
some
obvious
challenges
which
are
very
apparent
and
that
should
be
looked
at,
then
the
icon
here
that
I'm
using
for
delete
for
revoke
it's,
it's
used
for
delete
for
revoke
I,
couldn't
think
of
like
what
could
be
a
better
representation
of
an
icon
here
and
lastly,
now
that
this
has
been
split
into
two
parts:
the
creation
flow.
B
A
So
should
we
just
go
through
the
question
here
that
you
put
before
this
meeting?
Let's
see
the
wisdoms
that
we
covered
this
and
then
I
think.
The
next
item
that
we
haven't
cover
is
like:
do
you
have
any
suggestions
for
better
components
that
can
be
useful
reaction?
So
I
have
a
question
here
like
what
do
you
mean
by
action?
Is
it
the
icon
button
that
could
copy
and
revoke
or
the
other
action?
Do
you
mean
here.
B
I
don't
mean
like
this
very
special
specific
options,
but
other
the
tasks
that
we
are
allowing
them
to
do,
and
one
thing
that
I'm
very
sure
is
going
to
change
is
how
I'm
presenting
the
summary,
because
this
is
just
like
I've
kind
of
winged
it,
and
this
does
not
comply
with
pajamas
at
all.
So
I
would
really
like
to
know
if
there's
a
similar
summary
presented
elsewhere
in
gitlab,
that
I
could
look
at
and.
C
Yeah
I
have
one
feedback.
Let
me
move
my
comment
here
because
I
didn't
know,
I
also
didn't
understand
what
I
thought
actions
you
were
talking
about.
You
know
copy,
delete,
I,
think
just
by
looking
at
it
right,
I
think
it's
it
personally
as
a
question.
How
often
are
people
are
we
expecting
users
to
go
into
this
View
and
then
create
a
secret
edit
like
copy
that
value,
not.
B
B
And
one
thing
I
want
to
highlight
like
for
POC,
we
had
a
discussion
that
maybe
we
don't
want
to
like
open
up
the
even
the
project
secret
space
to
developers.
Just
yet
because.
A
B
Doing
anything
with
secrets,
so
it'll
probably
not
allow
them,
and
maybe
in
MVC
when
we
bring
up
more
customization
to
permissions,
we
can
rethink
this,
but
it's
only
going
to
be
the
maintainer
and
the
owner
who
will
be
taking
these
calls
and
security.
I
have
so
far
included
that
maybe
yes,
they
would
want
to
access
a
secret
page
to
maybe
do
an
audit,
a
security
audit.
C
Okay
yeah,
so
if
you
go
yeah,
if
you
go
to
your
prototypes
this
view
here,
where
you
click,
let's
say
on
the
edit
button
right:
if
there's
an
edit
button
there,
then
you
go
to
the
this
new
secret
view.
C
My
comment
here,
my
suggestion
is
this-
could
be
simplified
and
become
a
model
right
similar
to
what
we
already
do
in
the
settings
patterns
I
feel
like
because
it's
such
a
small
interaction
and
a
small
step
that
people
are
not
like
what
you
said:
we're
not
expecting
them
to
come
here
every
day
and
have
to
fill
in
the
details
and
review
things.
I
I
think
it's
it's
a
burden
that
you
have
two
pages
to
do
such
a
small
action.
C
So
my
suggestion
is:
here's
a
you
know:
experiment
with
the
model-
maybe
you
have
already
done
so,
but
I
also
think
that
it
would
simplify
it
for
both
development,
but
also
the
navigation
back
and
forth.
So
you
don't
have
to
to
create
more
pages
Etc.
That
makes
sense.
C
A
Think
it's
real
relevant
comment.
Sorry
I
interrupted
someone,
no
no
go
ahead.
Oh
yeah,
so
I
mean
like
it's
not
like
very
similar
patterns,
but,
like
you
have
some
code
box
inside.
So
this
reminds
me
of
something
when
we
fetch
the
French
when
we
open
the
Mr
and
then
when
we
try
to
fetch
the
branch
and
check
out
there
is
the
model
shows
up
how
you
fetch
this
branch
and
then
try
to
start
working
on
this
I.
Think
maybe
you
could
see
those
pages
because
I
made
some
changes
at
the
time.
C
With
a
summer
review,
that's
what
you
mentioned
and
then
I
don't
wanna.
Take
over
all
the
conversation
here,
but
I
didn't
realize
until
I
started,
seeing
what
video
I
was
going
to
show
that
my
questions
have
a
have
a
place
in
the
agenda
and
then
your
second
anyone
before
I
continue.
Maybe
anyone
wants
to
to
talk
about
the
components
or
at
least
the
flow
that
you
think
I
presented.
D
C
I
can
go
over
my
comments,
then,
and
then
others
can
fill
in
the
the
conversation
and
then
I
thought
about
a
future
Barbie,
because
when
you
start
talking
about,
I
was
looking
at
those
labels
and
I'm
like
what
are
those
in
this.
Yes,
so
you
have
that
here
at
this
level,
but
then
the
other
prototypes
it
didn't
have
when
you
start
showing.
C
Okay,
okay,
yeah,
because
when
I
started
looking
at
these
labels
here
for
inherited,
and
then
you
have
Dev
environment
right,
because
these
are
going
to
be
like
the
things
in
a
way
that
classify
that
yeah,
you
also
attach
value
to
the
to
the
secret
to
this
variable.
Based
on
that
and
when
I
saw
that
page
I
was
like
okay,
then,
why
is
this
a
label
added
under
to
the
secret,
like
in
a
secret
column?
D
C
A
B
This
is
a
question
that
I
think
I
should
add
to
the
technical
discussion,
because
so
far
secrets
are
not
very
like
they're,
not
the
first
concerns,
but
I
really
want
to
understand,
like
in
the
context
of
git
lab.
How
important
would
environments
feel
your
secrets.
C
If,
if
you
look
at
her
Runner
Fleet
I'm
gonna
try
to
find
out
the
Prototype,
she
has
also
like
multiple
labels,
and
my
concern
here
is
that
one,
if
you,
if
you
can
have
like
I,
don't
know,
100
environments,
I,
don't
know
multiple
pipelines,
especially
if
it's
inherited
right.
If
it's
inherited
secret,
the
UI,
it's
gonna
break.
C
If
you
have
all
these
labels
there
right
and
also
if
this
is
so
relevant,
should
it
be
I,
don't
know
at
a
different
level
right,
not
information
attached
to
the
name
of
a
secret
or
like
how
we
are
calling
that
variable
in
your
head.
You
want
to
add
something
to
you.
A
That
was
exactly
my
question
because,
like
so
I
don't
know
yet
and
then
I
think.
Of
course
you
need
to
check
in
with
your
engineers,
but
maybe
in
case
users,
let's
say
want
to
filter
by
the
environment,
and
then
they
want
to
see
those
Secrets
inside
then
I
think
it
makes
sense
to
have
this
into
the
different
information
level.
So
that
because
like
currently
it's
more
like
attached
to
the
secret
name,
so
yeah
I
think
it's
worse
to
check
that
yeah.
C
Okay,
I'm
gonna
link
here
to
one
of
Gina's
prototype
for
I.
Think
it's
the
runner
detail
page.
Let
me
where,
where
are
we
I,
think
we're
around
here
in
the
agenda
yeah?
So
if
you
look
at
this
one-
and
it's
always
here,
they
probably
tries
to
navigate
someone
else's
figma
file.
C
It's
very
organized
Gina,
that's
not
the
feedback,
but
it's
just
the
mental
model
is
different.
Okay
here
here
it
is
settings
she
has
that
yeah.
So
if
you
zoom
in
on
this
one,
that
is
highlighted
the
the
first
one
details,
yeah.
C
Zoom
in
there
and
you
see,
I
think
it
tags
it's
in
a
way
what
environments
will
be
for
you.
You
see
yes,.
D
C
There's
the
detail
for
you
and
here's
like
over
a
few.
She
has
the
let's
see
yeah
if
you
click
on
my
face
there
on
figma
you'll
be
able
to
see
what
I'm
looking
at
yes
yeah,
here's
she
has
a
status,
but
I
think
that
for
for
you,
perhaps
it's
something
like
that.
Like
I,
don't
know.
B
Environment
yeah,
so
for
runners
the
status
is
really
important.
Maybe
for
Secrets
the
labels
that
I
have
added.
They
are
not
half
as
important.
C
Yeah,
you
could
have
a
it's
just
like
when
we
have
what
we're
having
issues
or
you
know,
epics
and
you
have
that
overview.
The
list
view
you
don't
have
in
every
list
view
item
or
in
every
table
column
like
all
the
data
that
you
know
we
can
assign
to
an
issue.
So
maybe
that's
something
for
the
filter,
so
not
showing
you
why?
What
other?
What
do
others
think.
B
Right
so
like,
if
I
go
to,
let's
say:
here's,
then
how
we
like,
we
still
let
people
filter
by
certain
labels,
but
they.
B
Okay,
I'll
clarify
that
with
the
team
and
then
see
how
this
can
be
improved
and
if
this
is
like
absolutely
necessary
and
useful
to
provide
this
information
to
you.
C
D
Just
between,
like
the
inherited
label
and
the
environment
label,
is
there
a
reason
they're
this,
because
those
two
seem
very
different
and
when
I
was
looking
at
it,
it
seemed
like
they
were
the
same
category.
So
I
was
wondering:
is
there
a
reason,
they're
the
same
color
visually
or
because
I
did
see
in
genus
mocks
too
everything
was
blue,
so
that
might
have
just
been
from
my
misunderstanding
of
this,
but.
B
So
for
Gina's
mock
like
these
ones,
I
think
colors
and
labels.
They
can
be
mistaken
as
status.
So
that's
why
I
tried,
keeping
everything
neutral
and
yeah
that
that's.
That
was
the
only
reason.
D
Cool
I
was
just
curious
if
there
is
a
reason
between
that
or
not.
B
Yeah
I
still
have
to
polish
out
a
lot
of
things
here,
and
this
was
also
feedback
by
Michael
that
like
Maybe,
because
the
list
can
go
really
long
and
if
I'm
auditing
I
would
probably
only
want
to
look
at
the
project
secrets
for
now
and
not
get
confused
by
the
group
ones,
which
are
also
part
of
the
list.
So
I've
added
this
small
filter
effect.
Of
course
it's
not
going
to
make
it
to
the
POC.
C
Oh,
this
is
curious
because
a
show
project,
Chris
and
all
secrets.
So
this
is
like
a
filter,
indeed
not
just
that,
but
if
you
scroll
a
little
bit
to
the
left
on
the
tabs,
you
have
secret
and
audit
log,
but
then
you
also
have
audit
log
for
each
individual
Secret
in
this.
In
the
secret
view,
what
does
the
the
audit
log
page
show
and
why
not
have
like
Secrets
like
project
Secrets
or
all
secrets
you.
A
A
A
C
Yeah,
because
I'm
thinking,
like
I'm
thinking,
I'm
here
I'm
a
user
I
created
a
secret.
Oh
I
want
to
see
audit
log
I
want
to
see
like
I,
don't
know
something
is
fairly
in
my
pipeline.
I
want
to
see
if
someone
has
changed
a
particular
secret
value,
because
I
cannot
see
this
the
secret
value
anymore
right
so
I
go
to
audit
log
page
and
then
I
still
have
to
do
a
search
to
find
the
secret
information
in
the
audit
log
to
see
what
happened
with
that
particular
secret.
C
You
know
what
I
mean:
that's
what
I'm
thinking
as
a
user,
I
click
audit
log
and
then
what
do
I
see.
Do
I
see
just
a
log
of
everything
that
happened
in
with
all
the
secrets.
I
still
have
to
use
the
search
and
the
filter
to
see
like
okay
show
me
only
for
client
ID
when
I
could
just
go
here.
Click
client,
ID
and
see
the
audit
log
for
that
particular
secret
right
right.
B
I
have
like
a
counter
case
for
that
as
well.
I
mean
what
you
said
is
really
relevant,
that
individual
or
other
Lobby
is
helpful,
but
I
feel
that
you
need
both
because
to
figure
out
like
what
has
really
changed.
If
the
collective
audit
log
is
not
available.
C
Shouldn't
I
mean
if
it's
a
requirement
of
course,
but
for
example
when,
whenever
with
something
changing
their
release,
I
don't
know
I,
created
a
release
item
and
then
Emily
went
in
and
edited
that
release
and
you
know
changed
the
release.
Notes.
If
you
go
to
the
audit
log,
it
shows
there
like
the
project
audit
log,
so.
A
B
B
Yeah
I
remember
that
even
for
this
thing
for
variables,
that's
the
page
that
users
are
currently
using
I
mean
they're
asking
for
an
audit
log
for
variables,
but
they
are
currently
using
the
project
audit
log
to
see
so
it
does.
It
is
helping
them
to
some
extent,
so
I
definitely
don't
want
to
replicate
that
thing.
That's
a
good
point
and.
A
Emily
and
I
yeah
put
something
in
this
in
the
talk,
so
my
first
thought
was
like
just
X
marked,
but
I.
Don't
know
it
might
be
not
clear
like
because
we
already
use
this
and
like
clearing
the
keyword
in
the
filter
bar
and
then
like
anyways,
so
so
frequently
used.
So
I
was
like
I'm,
not
sure
like
thinking
faith
and
then
I
felt
that
Emily
has
also
another
idea
like
a
verbalized
family
yeah.
D
So
I've
seen
her
vote.
I
forget
where
I've
seen
this
but
I've
seen
it.
The
best
I
could
explain,
was
an
arrow
doing
a
U-turn
I,
don't
know
if
this
is
actually
in
pajamas
or
one
of
our
icons,
but
it
was
just
where
what
I've
seen
before
when
I'm
revoking
something
was
the
psychon.
C
D
C
C
B
C
Yes,
yeah.
B
C
C
A
B
A
B
A
B
Think
it
makes
sense
tooltip
on
the
button
when
I
hover.
Oh.
C
C
How
do
you
call
that
manage
like
in
the
detail
because
right
now
it's
copy
and
then
you
copy
the
value
right,
but
wait
a
second?
What
are
you
copying
here?
If
user
cannot
see
the
secret
if
they
don't
have
access
to
the
secret.
B
These
are
the
commands
to
access
it.
They
won't
be
able
to
see
the
value
they
can
only
access
it
in.
B
Yeah
yeah
there
is
a
tooltip
I've
added,
but
that's
very
like
heavy
on
words.
I
should
probably
change
it.
B
Also
because
it's
curl
command
I
learned
yesterday
from
the
team,
there
are
going
to
be
like
many
different
curl
commands
for
listing
for
revoking
for,
like
the
API
related
actions
like
get
so
it
can
be
as
straightforward
as
just
one
copy
command.
I.
Think
it's
going
to
be
a
split
drop
down
like
which
girl
command.
Do
you
want
to
copy.
A
B
And
also
the
example
that
you
shared
that
this,
what
we
see
when
we
are
checking
out
branches
for
NMR
yeah.
C
Preview
snippet
at
the
end.
Oh
okay,
that's
that's.
There's
a
little
comment
here.
Yeah,
that's
right
to
find
like
where
did
I
say
that
I
think
that's
something
different
too
right,
because
the
preview
snippet
at
the
end
requires
a
bit
redesigning
with
Pajamas
components
related
to
that-
and
that
was
my
my
comment
here,
because
if
you
show
the
UI
V,
it's
like
the
review
changes
right.
C
I
find
it
quite
heavy
for
such
a
small
flow,
because
you
have
an
overview
and
you
click,
add
new
secret
or
create
new
secret.
Whatever,
then
you
have
a
form
in
only
a
few
fields
and
then
you're
asking
the
user
on
this
whole
page.
To
like,
please
confirm
all
the
information,
but
can
they
do
that
already
in
the
previous
View
while
editing?
You
know
they
just
enter
the
field.
C
Maybe
they're
not
going
to
see
the
crore
command
I,
don't
know,
maybe
there's
something
that
once
after
they
create
something
here,
I
don't
know
you
can
get
a
preview
on
this
page
for
just
the
curricul
man,
but
not
the
whole
data
set
right
because
it's
just
date
expiration
and
then
roles
and
permissions.
It's
such
a
small
set
of
information
to
justify
I
think
having
a
whole
review
page.
B
And
also
like
this
curl
command
at
this
point,
so
initially
I
thought
that
maybe
we'll
show
a
snippet
of
how
this
can
be
used
in
the
in
the
pipelines.
But
this
particular
one
I
think
it's
better
to
show
this
after
the
secret
is
created,
because
it's
a
very
practical
command
for
using
the
secret
and
like
seeing
that
here
what
difference
it
would
make
to
their
decision
for
adding
the
secret
I'm.
Not
sure,
probably
nothing.
C
Yeah,
because
also
if
you
showed
that
before
and
then
I
haven't
added
a
secret
I
cannot
use
it.
So
imagine
imagine
someone
that
you
know
is
not
really
paying
attention
to
this
flow
and
they
say
oh
nice.
This
is
the
core
command,
I
can
use
and
they
close
the
tab
or
they
don't
save
this.
So
it's
a
bit
misleading
that
you're
showing
this
is
the
the
the
curl.
These
are
all
the
comments
I'm
creating
when
the
Secret's
not
there.
Yet
what
do
others
think.
A
B
B
A
C
She's,
like
I,
think
next
time,
let's
experiment
with
leaving
the
feedback
directly
in
figma,
like
kind
of
like
a
fake
gem
right,
everybody
leaves
the
comments,
because
now
we
go
dark
and
figma
yeah.
C
That
makes
sense.
Okay,.
A
A
Sure
do
you
have
any
other
questions?
Are
you
okay
with
just
stopping
the
report
and
talk
about
the
priceland
here,
I
think
I'm,
good,
okay,
cool!
So
all
the
record.