►
From YouTube: VC&C - Control Changes to Product Development Assets
Description
Version Control & Collaboration - Control Changes to Product Development Assets
Accelerate development, avoid confusion, and reduce rework by tracking and managing all your project assets. Development teams need a plan and a process to keep track of all the critical resources, files, and assets needed during planning, development, and delivery. Without a clear plan about how you’re going to manage these product assets, there’s a real risk that the wrong files, the wrong code, or wrong configuration can derail your project.
Learn@GitLab -
Get in touch with Sales: http://bit.ly/2IygR7z
A
Git
allows
a
wide
variety
of
branching
strategies
and
workflows
because
of
this,
many
organizations
end
up
with
workflows
that
are
too
complicated,
not
clearly
defined
or
not
integrated
with
issue
tracking
systems.
Since
many
organizations
new
to
get
have
no
conventions
for
how
to
work
with
it,
the
repositories
can
quickly
become
messy.
The
biggest
problem
is
that
many
long-running
branches
and
merge
that
all
contain
part
of
the
changes.
So
people
have
a
hard
time
figuring
out,
which
branch
has
the
latest
code
or
which
branch
to
deploy
to
production.
A
There
are
many
valuable
approaches
you
can
take,
such
as
making
a
production
branch
that
reflects
the
deployed
code.
You
can
deploy
a
new
version
by
merging
master
into
the
production
branch
or
creating
stable
branches
using
master
as
a
starting
point
and
branch
as
late
as
possible.
It
should
be
common
to
protect
the
long-lived
branches,
for
example
the
master
branch,
so
that
most
developers
can't
modify
them.
A
So
if
you
want
to
merge
into
a
protected
branch,
assign
your
merge
request
as
someone
with
maintainer
permissions,
permissions
in
git
lab
are
fundamentally
defined
around
the
idea
of
having
read
or
write
permission
to
the
repository
and
branches
to
impose
further
restrictions
on
certain
branches.
They
can
be
protected
by
preventing
pushes
from
everybody
except
users,
with
maintainer
permission,
preventing
anyone
from
force
pushing
to
the
branch
preventing
anyone
from
deleting
the
branch.
So
therefore,
like
that,
that
helps
you
make
any
branch,
a
protected
branch.
A
It
is
strongly
encouraged
to
get
code
reviewed
by
reviewer
as
soon
as
there's
any
code
to
review
to
get
a
second
opinion
on
the
chosen
solution
and
implementation
and
an
extra
pair
of
eyes
looking
for
bugs
security
issues.
Or
are
there
any
other
problems?
The
reviewer
can
be
from
a
different
team,
but
often
it's
someone
who
knows
the
domain
really
well
before
assigning
a
merge
request
to
maintainer
for
approval
merge.
A
A
Code
ownership
reduces
the
risk
that
the
absence
or
unavailability
of
any
one
developer
will
start
or
slow
work.
This
increases
the
chance
that
the
overall
design
results
from
sound
technical
decisions,
rather
than
from
some
kind
of
social
structure
retaining
the
privacy
and
integrity
of
your
data
is
crucial
and
you
can
use
a
GPG
key
to
sign
commits
made
into
a
repository
an
ailing,
dependable
data
protection
that
makes
it
easier
for
creating
digital
signatures
and
file
encryption
with
GPG.