►
From YouTube: Manage::Import UX Office Hours 2021-2-02
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
All
right,
so
we
are
having
the
manage
ux
office
hours
and
I
was
bringing
up
a
point
that
I
wanted
to
show
cassio.
So
I
let
me
just
bring
this
up
and
share
my
screen.
A
A
So
what
I
did
is
I
opened
this
link
in
github
edited
the
name
from
there
saved
it
came
back
to
get
lab
and
now
for
lack
of
better.
The
old
name
is
still
there,
as
well
as
whatever
I
named
it,
the
new
new
version.
I
guess.
A
Yeah,
but
it
makes
sense
because
you've
already
created
like
this,
this
doesn't
change
the
only
thing
that
changed
was
your
name,
the
name
from
github,
so
it
seems
like
this
line
still
should
exist
because
they
should
be
able
to
go
to
project
from
here.
But
what's
confusing
is
now
that
I've
changed
the
name?
I've
gone
back
to
gitlab,
I
keep
getting
404s
when
I
open
open
these.
These
are
all
the
ones
I
changed
yesterday,
the
day
before
whoops,
except
because.
B
A
B
A
Well
like
when
I
okay
well,
when
I
update
the
url
or
I'm
sorry
that
the
name
of
my
project,
the
url
does
change,
is
that
what
you're
saying
yes.
B
A
Well,
the
problem
I
had
is
when
I
would
go
to
the
github
project,
see
here's
here's
the
instance
where
this
is
happening
with
a
couple
of
my
projects,
so
I
just
went
to
what
was
it
yellow.
A
And
I
have
changed
the
name
data
infrastructure
which
is
down
here
somewhere.
I.
B
C
Sorry,
depending
on
how
you
renamed
the
project
on
github,
I
know
it
does
a
redirect
by
itself.
So
I
know
github
keeps
the
old
name
for
a
while
it's
not
forever,
but
for
a
while
after
you
renamed
the
project.
So
the
old
url
will
continue
work
because,
like
if
you
share
that
project
with
more
people
or
something
like
that,
it
keeps
redirecting
to
the
new
url.
A
C
But
just
just
for
me
to
to
be
sure
that
I'm
the
same
page,
did
you
go
in
the
github
settings
and
read
rename
the
the
repository
out
there
on
the
project
in
the
github
settings
or
you.
A
C
A
A
It's
confusing
so
my
hair.
Let
me
bring
over
my
sigma
file
and
walk
you
through
so.
A
Well,
okay,
let
me
walk
you
through
this,
so
if
a
user
navigates
to
the
import
groups
page,
they
notice
there's
a
mistake
in
the
name
of
the
project
from
github.
So
now
they
have
to
navigate
to
github
to
change
the
name
of
the
project.
B
A
Yes,
so
what
my
suggestion
is
that
when
a
user
after
a
user
comes
back
from
renaming
it
and
get
github,
we
had
we
disabled
a
link.
So-
and
actually
you
wouldn't
see
this,
but
we
just
create
a
read
only
so
they
aren't
going
to
be
directed
to
a
404
page
or
they're
not
going
to
be
directed
to
project
that
isn't
named
the
same.
Does
that
make
sense,
because
by
me
name
renaming.
B
I,
like
the
first
part
of
that
sentence,
and
that
is
if,
if
we're
gonna
take
you
to
a
404,
maybe
we
should
try
and
handle
it
better,
maybe
but
like
let's
just
leave
that
to
the
side,
but
if
I've
actually
renamed
or
fixed
a
typo
in
a
in
the
name
for
a
project
in
github
like
it's
kind
of
nice,
that
gitlab
knows
that
yeah.
This
particular
project
has
been
imported
like
just
because
your
name
changed.
The
name.
Doesn't
change
change,
what
the
project
is
like
who's
in
it.
What
work
is
in
there?
B
What
it's
for,
like
all
these
things,
like
the
gist
of
that
the
the
purpose
of
that
project
is
exactly
the
same
like
we
just
changed
the
title
for
it,
but
it
is
that
project
that
project
has
been
moved
into
gitlab.
So
if
we
actually,
in
fact,
are
telling
you
that
yeah,
you
have
already
imported
this
once
under
this
name,
I
don't
think
that's
a
bad
message.
I
think
that's
kind
of
a
nice
to
know.
B
B
They
will
do
that,
whether
it
takes
them
to
404
or
a
new
redirected
name,
they
will,
if
they
click
on
that
their
intent
is
to
see
what's
behind
that
link
and
if
we're
not
allowing
them
to
click
on
that,
they
don't
know
why.
That
is,
they
will
copy
and
paste
that
url
they
will
still
do
it.
B
It's
just
like
gonna,
be
you
know
three
extra
steps
for
them,
but
if
that's
what
the
user's
intent
is,
I
tend
to
err
on
the
side
of
not
stopping
the
user,
be
able
to
exercise
their
intent
like
there's
nothing
destructive
about
them
going
there
and
seeing
yep.
This
project
no
longer
exists
like
it
exists
at
some
point
in
time
it
either
got
deleted
or
who
knows
what?
But
you
know
it
did
exist,
and
now
you
can
at
least
I
mean
404
is
informational.
B
B
A
B
I
don't
think
it
tells
them
why
that
is
like.
If
we
could
provide
the
full
story
and
a
workaround,
then
I
think
you
know
we
might
want
to
disable
their
ability
to
do
that
because
we're
like.
Oh,
no,
no,
you
deleted
this
or
you
renamed
this
or
here's
a
new
link
or
don't
go
there.
I
mean
if
we
give
him
a
reason,
but
if
we're
just
leaving
it
like
that
without
any
reasoning
and
they're
like,
but
I
really
want
to
go
there,
they're
just
going
to
copy
and
paste
it.
B
C
Actually,
at
first
I
was
sending
to
leading
leaning
to
not
having
a
link,
but
I
I
was
checking
the
code
and
if
the
path
comes
it's
because
in
the
api
of
github,
the
repository
yet
exists.
So
we
built
this
ui
as
far
as
I
could
understand,
on
a
quick
look
in
the
code
based
on
the
github
api.
So
although
it's
it's,
it's
a
link
for
a
404
which
I
agree.
It's
not
very
useful
or
interesting
to
the
end
user,
but
is
is
a
url,
is
a
repository
path
that
github
is
returning,
so
I
I'm
not.
C
I'm
not
sure.
I
think
we
could
do
something,
but
I
think
the
effort
to
do
something
it's
higher
than
the
return
the
cost
benefit
on
that.
I
I'm
not
sure
it's
worth
it
since
it's
something
that
already
comes
from
the
github
and
it's
probably
just
something
that
either
github
is
caching
or
re-are
caching
somewhere.
So
it
might
go
away
in
a
few
days
time.
A
C
All
that
said,
I
have
another
question:
did
you
test
like
importing
a
repository
then
deleting
the
repository
on
github?
If
it
still
appears
in
there
because
should
be
a
similar
behavior
with
a
dimension.
A
Yeah,
let
me
I
don't
think
I've
tried
deleting,
but
I
can.
C
C
Wait
what
that's
right
good
because
like
if
we're
deleting
something
from
github
and
it's
not
appearing
there-
it's
because
github
is
deleting
for
real
from
the
api
as
well.
It's
probably
cleaning
some
caches
or
somewhat
now,
if
you
delete
on
github
and
still
appears
in
there,
it
might
be
that
we
are
caching
on
our
site,
and
that
would
be
bad
because
I
think
this
ui
should
be
viewed
without
caching,
at
least
for
the
first
time.
C
I
don't
know,
I
I'm
not
sure,
what's
the
best
solution,
I'm
just
saying
that
you,
as
far
as
I
can
see,
we
use
the
api
to
build
the
ui.
The
the
list
so
filtering
that
ui
can
can
be.
Tricky,
cannot
be,
and
I'm
not
sure,
I'm
not.
I
don't
know
from
the
top
of
my
mind
the
returns
of
the
api,
if
there's
something
like
renamed
or
some
kind
of
attribute
like
that,
we
could
investigate.
C
But
in
any
case
I
don't
think
the
the
big
problem
to
the
users
most
of
the
time,
but
in
myself
trying
to
put
myself
as
a
user
who
imports
a
lot
of
repositories.
I
don't
think
to
be
honest,
I
would
look
too
much
to
things
that
I
already
imported.
If
I'm
going
to
this
page,
I'm
probably
trying
to
look
more
to
things
that
I
want
to
import.
C
So
maybe,
if
I
see
like
a
a
repository
that
I
thought
I
already
imported
and
it's
available
to
import,
that
would
be
weird
and
that's
also
the
case,
but
the
things
that
I
already
imported,
I
think
most
of
the
users
won't
be
too
concerned.
If
those
things
are
404
or
not,.
A
B
I
was
going
to
say
we
already
have
a
feature,
that's
coming
down
or
eventually
will,
and
that
is
the
ability
to
view
import
history
like
I
feel
like
at
that
point
when
we
split
the
data
off.
These
are
all
the
things
that
you've
done
before.
Historically,
these
are
things
you
imported
when
you
imported
who,
how
here's
a
link
and
if
it
doesn't
exist
there
anymore.
Well,
that's
because
you
deleted
it
like
I
don't
care.
So
when
we
split
the
historical
data
from
these
are
the
things
you're
actually
on
right
now.
B
I
think
this
will
be
cleared
up
somewhat,
so
I
would
probably
want
to
revisit
our
logic
once
we
do
implement
the
history
page,
because
I
think
some
of
this
could
live
on
the
history
page
and
be
relevant
there
forever,
and
the
other
feel
that
I
have
here
is
like
yeah.
There
seems
to
be
like
a
missing
feature
here.
I
think
you're
on
to
the
fact
that
there's
a
missing
feature,
but
it's
a
missing
feature
for
github,
not
for
gitlab
like
and
they
may
implement
something
like
you
know.
B
We
we
get
this
link
from
them
or
we
keep
like
whatever
it
is
like.
We
have
this
link,
we
don't
know
if
it's
gonna,
take
you
to
four
or
four.
If
it's
gonna
redirect
you
to
a
new
thing
or
if
it's
gonna,
take
you
to
a
new
page
that
says:
hey
there
used
to
be
something
there
used
to
be
a
project
you're
not
deleted.
Maybe
they
implement
a
different
page
instead
of
the
404.
B
It's
something
that
says
delete
a
project
this
the
project
was
deleted
by
cassio
three
days
ago,
and
that
would
be
an
improvement
to
their
404,
whereas
just
take
you
to
like
yeah
there's
nothing
here
to
see
he
was
like
well,
there
used
to
be
something
here
see,
but
they
may
implement
that,
like
we
don't
control
that
and
we
shouldn't
like,
we
should
let
you
go
there
and
then,
whatever
their
experience
is
with
things
that
you
deleted.
There
is
not
our
concern
in
theory,.
A
B
So
that's
yeah,
that's
kind
of
how
I
see
it.
I
really
don't
want
to
be
compensating
for
the
fact
that
github
doesn't
have
that
feature
because
they
may
tomorrow
have
a
feature
that
yeah
tells
you
more
about
it
on
that
page.
So
we
still,
I
would
say
we
take
you
where
they
told
us
and
now
you're
in
github,
and
if
you
don't
like
the
fact
that
you
deleted
something
but
they're
not
telling
you
to
leave
they're
telling
you
404,
there's
nothing
here.
That's
really
a
feature
for
github
to
implement.
A
Yeah
fair
enough-
and
we
are
at
time.
A
C
I
I
I
I
left
to
say.
Oh
sorry,
I
was
looking
the
the
api
here
and
maybe
we
could
just
check
what
url
we
are
using
to
build
this
page,
because
I
I'm
seeing
here
from
the
github
api
that
actually
they
return
a
bunch
of
different
urls.
C
So
maybe
we
are
using
the
wrong
one
or
something
like
that.
But
this
is
something
that
I
can
check
right
now,
just
to
be
sure
that
we
are
not
using
something
some
outdated
field
or
something
like
that,
because
maybe
it's
something
silly
and
we
just
let
it
go
away.
Yeah.