►
From YouTube: Project Import Walkthrough
Description
Jeremy Watson walks through importing a project onto GitLab.com.
Action items from this walkthrough at https://gitlab.com/gitlab-com/Product/issues/650.
A
Hey
there,
I'm
jeremy,
I'm
a
product
manager,
your
good
laugh,
your
kid
lie:
we've
been
doing
product
walkthroughs
a
little
bit
more,
which
are
just
quick,
show
intelligence
sessions
around
different
areas
of
the
product.
You
know
showing
off
kind
of
our
experience
or
expectations
and
kind
of
what
we
actually
saw
in
the
application.
We
try
to
accomplish
a
certain
task
right
now.
A
I
just
walked
through
a
quick
like
project
import-export
kind
of
tasks
which
I'll
show
off
kind
of
later
in
the
video,
but
overall,
like
I
was
interested
to
kind
of
understand
what
it
would
be
like
if
I
imported
a
project
from
both
another
gitlab
self-managed
instance,
and
also
a
good
bucket
cloud
and
try
to
push
that
into
get
lab.
Comm
overall,
like
I
give
the
overall
experience
can
have
a
BB
the
single
project
and
export
import
experience
was
pretty
fast,
free,
straightforward.
There
was
some.
A
A
Where
you
know
this
was
a
scenario
and
a
single
project
which
I
think
is
fine,
but
if
I'm
a
mature
gitlab
instance
with
hundreds
of
users
and
hundreds
of
projects,
you
know
scripting
to
kind
of
like
iterate
through
this
using
our
project,
export,
import,
API,
I
think,
would
become
pretty
challenging
and
would
take
a
lot
of
time.
I
think
that
you
know
I'd
love
to
see
better
or
kind
of
capabilities
around.
You
know
importing
and
exporting
at
the
group
level,
as
well
as
just
a
better
kind
of
user
experience
around.
A
You
know
we're
able
to
offer
like
this
really
cool
kind
of
import.
All
experience
from
bitbucket
cloud
there's
no
real
reason
why
we
can't
do
that
for
self-managed
to
get
lab,
comm
I,
don't
think
I
think
our
documentation
should
also
be
clear.
There
are
a
couple
of
questions
that
I
had
kind
of
like
moving
through
the
docs,
or
it's
that
there
were
a
little
bit
confusing,
especially
around
like
user
mapping.
Forget
lab
comm
I
think
could
use
a
little
bit
of
clarity.
A
I
ran
into
a
bug
where
I
was
trying
to
import
a
project,
and
it
was
a
hard
stop.
I
wasn't
able
to
kind
of
complete
that
task
without
some
googling
I
was
able
to
find
another
get
lab
issue
and
which
had
some
workaround
information,
which
was
great,
but
ideally
we
shouldn't
have
run
into
that
and
I
think
last.
The
last
three
items
were
items.
A
We
were
already
aware
of,
like
when
you're
importing
a
project
into
get
lab,
calm
the
you're
not
able
to
really
attribute
its
kind
of
user
objects
to
specific
users
where
the
user
that
is
performing
the
project
import,
has
all
the
merged
requests
and
issues
and
pipelines
all
associated
with
them
as
the
author.
So
if
you
are
a,
you
know,
a
get
lab
instance
with
many
different
users,
all
contributing
different
things,
having
an
import
experience,
which
is
attributes
all
that
work
kind
of
to
one
person
who
would
the
the
importer
to
the
to
the
project?
A
Importer
is
less
than
ideal,
so
I
think
that
there's
definitely
room
for
us
to
be
able
to
have
a
better
import
experience
to
be
able
to
perform
that
mapping
and
map.
Very
those
various
objects
to
you
know
users
and
there's
also
some
missing
items.
The
import,
I
think
semi.
These
items
that
we
leave
out
of
the
project
import
makes
sense
like
build
artifacts,
for
instance,
which
can
obviously
increase
the
size
of
the
import
considerably.
A
If
we
decided
to
include
those,
there
are
other
things
like
you
know:
CI
variables,
for
instance
or
others
that
we
could
consider.
You
know
trying
to
include
there's,
obviously
some
some
security
questions
around
around
some
of
it
that
we
need
to
be
able
to
answer.
But
overall,
you
know,
there's
probably
more
we
could
be
able
to
do
to.
A
You
know
make
the
artifacts
that
we
kind
of
export
like
as
complete
as
we
can
make
them,
and
then
lastly,
I
think
New
York's
needs
improvement.
There's
some
there's
some
areas
that
you
know
we
can
can
make
that
UX
better.
There
was
one
there's
a
couple
of
error
messages
that
were
confusing
when
I
ran
into
that
hard
stop
being
space
non-valid,
it
was
really
confusing,
is
to
kind
of
what
to
do
next.
A
A
B
A
My
green
projects
to
get
love
instance,
its
sounds
pretty
good
list,
a
bunch
of
things
here,
migrating
from
cell
phones
to
get
allowed
to
be
a
lab,
calm
cool.
If
you
only
need
to
migrate
repose,
you
can
import
each
project
by
URL,
but
issues
and
merge
requests
can't
be
imported.
So
I
would
like
to
keep
those.
So
if
you
want
to
retain
all
my
data,
you
can
use
the
import/export
feature
to
export
projects
or
self
opposed
to
get
out
and.
A
It's
unfortunate
assumes
all
users
have
already
been
my
created.
The
user
conducting
the
import
will
take
play,
take
the
place
of
all
references
to
the
missing
users,
not
condemned,
not
sure
what
this
approach
assumes
all
users
from
the
self
hosted
instance
of
argument.
Migrated
means
it's.
You
need
to
migrate.
All
data
over.
You
can
leverage
our
API
to
maker
from
so
close
to
da
live.com.
The
order
of
access
to
migrate
from
cell
phones
to
collab
is
the
following.
A
You
just
creeps
projects
probably
feels
cool,
keep
in
mind,
limitations,
import/export
feature,
you
know,
still
need
a
migrate
over
your
container
industry
or
a
series
of
doctor
pulls
and
rerun
any
CI
pipelines
to
achieve
any
build
artifacts.
Okay,
according
to
this
there's
some
stuff,
that's
gonna
be
exported
project
de
wiki
project
uploads.
So
this
the
following
items
will
not
be
exported.
They'll
trace
it
and
artifacts.
So
I
go
softer
with
my
pipelines
and
we
recreate
those
container
registry
images
see
a
greater
pull.
B
A
B
A
For
an
expert,
so
I
think,
what's
what's
really
not
clear.
Here
is
the
fact
that
if
you're
moving
over
to
get
lab
comm,
you
know
you
big
migration
of
users
and
get
lab.
Comm
is
something
that's
an
admin
assistant
of
tasks.
So
this
is
not
something
that
makes
it
very
clear
that
this
is
kind
of
the
primary
migration
path,
which
is
where
the
users
having
to
migrate
over
and
the
user
could
actually
conducting
the
import
will
take
it
gets.
A
It
takes
place
of
all
the
references
to
the
missing
users,
so
that
part
is
not
especially
clear
here,
so
I
think
our
documentation
can
probably
use
a
facelift
here.
The
import/export
feature
to
export
projects.
So
let's
give
that
a
try
any
existing
projection.
Ex4
of
the
related
data.
Is
he
also
import
important
notes?
Importing
is
not
possible,
it
must
be
an
email
application
settings.
A
A
B
A
A
A
Importing
the
project
for
the
Kitab
projects,
the
first
import
forum
and
create
a
new
project,
click
on
gillip
export,
so
over
here
I've
created
an
account
on
get
lab
calm,
and
this
is
what
I
kind
of
see
after
registering
and
logging
ends.
It
says
please
check
your
email
to
verify
that
you
own
this
address,
unlike
the
power
of
CI
CDA,
didn't
receive
resend
it
free
trial.
A
A
A
A
A
B
A
A
This
particular
project,
so
so
in
conclusion,
I
mean
this
is
this
was
okay
I
mean
I?
Don't
I
think
that
the
whole
process
could
have
been
a
lot
smoother
as
someone
who
was
just
who
just
joined
get
lab
comm
for
the
first
time,
I
was
looking
to
import
my
project.
There
wasn't
like
a
great
option,
a
very
clear
way
of
being
able
to
do
that.
A
The
documentation
wasn't
clear
in
terms
of
what
like
what
steps
I
needed
to
take
and
what
limitations
there
were
I
think
it
was
kind
of
a
little
bit
confusing
in
terms
of
what
I
needed
to
do
in
terms
of
user
mapping.
I
would
like
to
try
this
with
a
project
that
has
a
are
like
an
already
created
and
it's
using
private
runners
and
then
also
has
a
CI
yeah.
A
Don't
think
that
that
should
really
matter
so
I
think
that
I'll
create
some
issues
to
be
able
to
kind
of
repair
some
of
those
issues
and
then
I'll
work
on
making
a
more
elaborate
walkthrough
kind
of
later
on.
I
am
kind
of
curious
about
moving
from
bitbucket.
So
I
have
like
a
very,
very,
very
bare-bones
test.
Repo
here
and
I'm.
Curious
is
kind
of
what
the
experience
is
like
there,
if
it's
any
better
or
worse
so
I'm
gonna
go
ahead
and
try
and
search
for
that
again.
Some
moving
from
bitbucket.
B
A
A
B
A
A
That's
actually
nice,
it's
nice
to
do
that.
It
shows
off
that,
like
we
don't
support
mercurial
and
you
know
to
convert
those
to
those
projects
to
get
before
you're
able
to
do
the
import
flow
again.
That's
that's!
Pretty
good
I,
like
that.
You
know.
There's
party,
a
nice
import
all
compatible
projects
button
here
that
I
can
use
I
had
the
chance
to
read,
configure
the
project
slugs
whenever
I
want
to
and
then
import
those
individually.
So
let's
just
click
this
and
see
what
happens.
B
A
And
I'm
not
really
sure
what
I'm
supposed
to
do
at
this
point,
I
see
this
spinner
is
still
working
for
some
reason,
even
though
everything
is
done
so
I
guess
the
process
is
finished
and
now
I
can
click
into
my
repository
I'm
interested
in
pretty
good.
Up
into
this
point,
I'd
like
to
see
we
have
some
sort
of
like
finished
state
here
or
like
Next
button
to
be
able
to
showcase
that,
like
the
you
know,
the
work
is
finished
and
like
we
can
do
something.
Go
do
the
next
thing.
So
click
into
this
looks
good.
B
A
Is
all
fine?
My
issue
that
I
have
here
looks
like
it
was
connect.
It
was.
It
was
moved
over,
so
I
did
have
an
issue
created
by
by
my
username
on
the
bucket
cloud
and
is
allocated
to
my
username
that
I
have
on
Geylang
comms,
that's
as
I
expected
under
the
documentation,
not
the
best,
if
I
have
hundreds
of
hundreds
of
issues
created
by
many
many
different
people.
So
that's
not
a
great
experience
so
overall,
like
it
was
a
decent
experience.
A
A
I'd
like
to
see
a
better
solution
kind
of
for
how
we
map
users
and
individual
artifacts
to
get
live
calm,
but
I
think
that
the
bug
that
we
kind
of
discovered
that
and
pointed
out
around,
like
importing
of
a
self
managed
to
get
lab
tarball
in
to
get
lab.
Calm,
I'd
love
to
see
us
kind
of
prioritize
that
and
I.
A
Some
issues
and
lots
of
room
for
improvement,
I
think
I'd
love
to
reread
this
to
rerun.
This
exercise
on,
for
both
a
more
complicated
kind
of
like
import/export
scenario,
to
see
kind
of
what
happens
with
a
more
mature
project
using
all
of
get
labs
features.
I'd
love
to
see
like
a
project
that
uses
like
all
ten
stages,
essentially
I've,
get
lab
and
see
kind
of
what
is
missing
whenever
we
try
to
import
and
export
that,
or
rather
export
and
import.
A
It
and
finally,
I
think
that
you
know
I'd
love
to
see
well
prioritize
more
walkthroughs
for
other
areas
and
manage
like
authentication
and
configuration
of
something
like
LDAP
and
in
say,
malign
a
based
identity
provider.
So,
overall,
not
not
bad,
but
I.
Think
that
there's
lots
of
room
for
improvement
so
we'll
get
it
working
on
some
issues
and
get
those
prioritized.
So
thanks
a
lot
for
watching
Cheers.