►
From YouTube: Import / Export Development
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).
B
Yes,
sir,
let
me
share
my
screen
so
not
too
long
ago,
I
had
this
ticket
about
group
level,
templates,
I,
don't
know.
If
you
guys
know
what
group
level
templates
are,
but
it's
wait.
I
mean.
C
B
I,
let
me
check
in
in
in
my
local.
B
But
basically
is
when
you
pick
a
project
as
a
template
for
other
projects.
Okay,
yeah
yeah
I
switched
branched
a
lot
lately.
So
it's
normal.
It's
not
it's
not
working,
but
it's
when
you
picked
a
project
as
a
template
for
another
project,
basically
and
how
it
works.
Is
that
it?
Basically,
if
you
pick
any
projects
in
in
the
application
as
a
as
a
group
level
template,
you
can
actually.
B
B
Like
some
information
on
how
to
set
up
there
is,
there
is
a
a
doc
for
that.
So
if
you
choose
any
repository
of
yours
as
a
group
level
template
what
it
does
is
actually
just
exporting
the
template,
the
the
the
repository
locally
and
re-import
it
into
yeah
and
re-import
it
into
whatever
group
or
whatever,
wherever
you
want
it
to
to
your
your
project,
to
be,
it
works
actually
the
same
as
a
fork
inside
the
application.
B
So
the
fork
does
exactly
the
same.
So
what
it
does
is
it's
import
exports
repository
and
it
re-imported
without
showing
it
to
the
user.
Let's
say
foreign,
so
how
you
can
so
I
had
some
of
these
points
of
the
settings
of
our
project
settings
to
add
into
into
the
project
template,
because
clients
were
exporting
templates,
but
they
didn't
want
to
wanted
to
copy
over
all
their
settings,
and
they
were
way
more
than
just
these
settings
in
the
original
scope
of
the
ticket,
but
we
we
reduced
it
yeah.
B
So
how
can
you
add
stuff
so
the
the
main,
the
main
thing
you
need
to
do
for
this
for
to
make
this
work
is
actually
working.
Inside
of
the
import
export
tml
file,
so
this
file
and
add
some
stuff
or
then
or
remove
some
stuff.
If
you
want
to
remove
some
stuff,
so
yeah
I
added
some,
the
options
that
were
missing
like
yeah
only
only
allow
merge
requests
to
be
merged.
If
the
pipeline
is
succeeded,
this
one
I
can
I
guess
I.
B
But
yeah,
it's
the
you
know
the
settings
to
to
only
allow
a
merge
request
when
the
pipeline
has
succeeded.
Well,
that's
this
one.
It
was
not
here
before
or
was
it
yeah
it
was,
but
it
was
a
method,
so
it
was
already
there,
but
it
was
a
method.
So
oh
sun
has
a
question.
A
B
I
don't
know
actually,
but
I
can
I
can
look
it
up.
Okay,.
C
E
C
B
B
So
that's
the
that's
actually
the
tree
so
inside
the
tree,
you
have
the
project
which
is
kind
of
the
route
our
project
has
labels.
Labels
has
properties.
So
that's
how
you,
let's
say,
set
up
the
the
associations
so
in
the
export
file
they
can
all
be
linked
with
each
other
for
do.
I
have
like
a
easy
another
easy
yeah.
So
like
project
has
issues,
issues
has
events,
events
as
push
events
payload,
which
are
all
like
associations.
B
It's
not
it's
not
pills
or
anything
that
is
that
should
be
copied
over
there
and
then
here
under
so
after
the
three
section,
you
have
the
included
attributes
and
that's
where
you
actually
put
the
the
fields
so
user.
We
just
want
the
ID,
the
public
email
and
the
username
for
projects.
B
B
This
one
was
not
in
neither
so
I
I
had
to
add
it
to,
and
this
one
I'm
not
sure
anymore,
but
yeah.
So
for
this
one.
The
interesting
thing
is
that
it's
actually
not
an
attribute
of
the
project,
but
it's
an
attribute
of
the
project
settings
and
the
project
is
just
delegated
to
the
project.
So
it
means
it's.
It's
a
method
that
points
to
the
project
settings,
so
the
developer
can
think
it
belongs
to
the
project,
but
it's
not
and
you
can
set
it
up
by
actually
adding
the
field
to
the
methods
here.
B
What
else
was
interesting
in
there
for
this
one?
It
was
pretty
easy,
so.
B
Has
normally
okay,
yeah,
so
group
level?
So
here
this
we
didn't
have
the
settings
for
everything
that
was
related
to
web
Hooks
and
it
was.
It
was
asked
by
the
the
clients
to
to
have
those,
but
the
trick
was
that
we
couldn't
do
it
directly
with
the
import
export
import
export
file,
because
there
was
a
lot
of
sensitive
data
and
encrypted
data
into
the
into
the
project
settings
class
into
the
webhook
class.
So
we
could
not
just
copy
it
over
by
just
showing
into
the
into
the
X
import
export
files.
B
Just
the
data
like
that,
and
because
it
could
like
cause
all
kinds
of
problems
and
people
could
like
export
the
projects
copy
whatever
they
want
in
the
in
the
web
books
and,
for
instance,
get
the
data
like
every
time
somebody
pushed
they
could
get
the
data
of
the
push
into
a
web
hook.
They
have
set
it
up
or
something
like
that,
so
it
was
pretty
dangerous.
B
So
what
we
did
is
open.
C
B
So
yeah
in
exporting
works
with
the
file
and
importing.
So
it
takes
all
the
information
of
the
file
and
it
uses
restorers
and
savers
to
build,
build
their
project
back
up
so
restores
just
built
an
instance
without
saving
it,
and
the
savers
saves
the
instance
like
in
the
right
orders
in
the
right
order.
B
B
And
I
just
copy
them
over,
like
like
like
this
here,
so
I
copy
all
the
files.
First,
all
the
fields,
first,
I
copy,
the
the
targets,
project
ID,
so
the
the
project
that
is
copied
over
and
then
I
nilified
all
those
encrypted
encrypted
crypted
Fields,
because
if
I
didn't
nullify
them,
it
would
have
had
the
same
value
as
the
priv
as
the
as
the
project
we
try
to
copy
over,
and
this
would
be
a
security
issue
too
and
then
I
yeah
I
just
said
set
them
up.
B
Yeah
like
that
and
yeah
there
we
go
so
it's
safe.
It's
safe
security,
wise
to
do
it
like
that,
and
is
there
another
one
that
was
kind
of
interesting
yeah,
but.
B
B
Like
here,
like
I
needed
to
copy
over
the
protected
branches,
I
I
needed
to
actually
copy
over
the
reference
of
a
protected
branch
and
an
ID
was
not
good
enough,
because
the
ID
of
the
protected
branch
of
the
previous
of
the
of
the
projects
we
are
copying
over
is
not
gonna.
Be
the
idea
of
the
protected
branch
of
the
new
new
Repository,
so
I
needed
to
use
the
branch
name
for
that.
So
if
you,
if
we
check
the
yaml
file,
all.
B
So
in
the
methods
of
the
approval,
approval
project
rules,
protected
branches,
it's
a
long
name.
It's
a
mouthful,
I've
put
the
the
method,
Branch
name,
so
it
would
show
up
in
the
in
the
in
the
exports
exported
file
and
then
with
this
Branch
name,
I
I
need
to
find
the
the
ID.
B
So
yeah
in
the
relationship
yeah,
so
I
I
take
the
the
branch
name,
I,
try
to
find
the
protected
branch,
and
normally
it
should
be
there
because
it
goes
through
the
file
from
from
top
to
bottom.
B
So
if
a
relation
is
at
the
top,
it
should
handle
this
relation
first
and
create
all
this
relation
and
restore
it
and
save
it
like
first
so
here
I
was
pretty
sure
that
I'm
pretty
sure
that
the
protected
Branch
would
be
here,
I
find
it
by
the
name
that
I
found
that
I
copied
over
from
the
the
file
and
then
I
can
set
it
up
as
the
reference
of
the
of
the
protected
brand
approval
protected
this
one,
the
the
joints
file
The
Joint
table.
B
So
sometimes
you
need
to
work
on
this
one
like
by
creating
yeah
in
setup
models
you
create
when
it's
when
it
hits
that
that
that
model
of
the
tree
set
it
up
like
this,
and
it
will
do
whatever
you.
B
A
F
So
yeah
common
from
my
side,
I,
was
I,
saw
this
like
expert
file
and
I.
Think
I
edited
it
a
couple
of
times,
but
to
be
honest,
I
don't
have
like
a
knowledge
about
how
exactly
it
works
like
I,
just
like
added
some
like
new
fields
to
that,
but
I
think
it
might
be
a
good
question
for
the
import
group
t,
because
I
feel
that
you
might
be
missing
like
when
we
create
a
new
field.
F
B
C
B
E
Something
else
that
you
could
do
as
well
and
facility
I'm
I'm
gonna,
ask
because
I
don't
know.
Is
there
a
particular
merge
request
template
that
gets
used
whenever
new
items
are
added,
because
if,
yes,
you
could
add
a
line
to
that
that
particular
form
and
say
hey,
you
need
to
go.
Add
this
to
this
file.
A
B
D
I
think
we
have
some
static
analysis
for
some
other
things,
but
I
don't
remember
which
one
I
I
guess.
It
sounds
like
all
models
file
or
something
like
this,
but
the
different
from
this
file
is
that,
as
Patrick
mentioned,
that
sometimes
the
data
is
sensitive,
so
you
can't
just
add
everything
there.
So
it's
like
should
be
a
customized
and
yeah,
but
you
know
some
static.
Analysis
might
be
useful
for
this.
One
I
agree.
B
That
there
is
actually
some
static
analysis
already,
but
they
don't
add
like
Fields
automatically.
You
need
to
add
them
like
when
it's
it
works
more
like
when
you
add
a
new
field
into
the
export
file.
It
checks.
If
the
field
is
also
in
the
picture
and
like
if
the
text
is
got,
the
tests
are
gonna
work
properly
and
are
gonna
catch
all
the
fields
that
are
in
the
import
export
file,
but
it
doesn't
yeah
it's
static,
so
it
doesn't
do
it
automatically
with
new
fields.
A
Patrick,
thank
you
very
much.
That
was
a
great
talk.
Thank
you.
Thank
you.
So
much
for
that
I'm
gonna,
stop
record
I
just
want
to
mention,
though,
that
so
the
next
week
is
Gavin
is
presenting
so
yeah
and
as
as
always,
you
know
it
can
be
anything
you're
working
on.
It
can
also
be
something
that's
not
even
actually
merged,
and
always,
if
there's
ever
to
you,
know
too
many
things
going
on,
we
can
skip.
So
thanks
thanks
a
lot
Patrick.
That
was
really
awesome.