►
Description
What are some characteristics of an efficient developer workflow? How do all stakeholders benefit? And, what does this workflow look like, in practice?
A
Hello,
my
name
is
Victor
Hernandez
and
I'm,
a
Solutions
Architect
at
gate
lab.
The
purpose
of
this
sales
level
of
presentation
is
to
address
the
question.
What
are
best
practices
for
a
developer
workflow
get
laughs,
provides
the
necessary
capabilities
to
accomplish
all
aspects
of
modern
software
development.
With
this
in
mind,
how
can
a
development
team
make
the
best
use
of
gitlab
through
this
brief
video
I
will
provide
you
a
recommended
best
practice
for
a
developer
workflow.
A
Let's
establish
why
the
question
is
important.
Consider
there
are
many
inputs
and
outputs
to
creating
and
delivering
great
software.
The
aim
of
an
efficient
software
development
workflow
is
to
automate
redundant
tasks.
This
reduces
context.
Switching
and
minimizes
clicks
to
simplify
and
enable
collaboration
for
stakeholders
following
the
workflow
becomes
natural
and
informs
users
of
actions
and
inputs
needed
to
reduce
the
it
takes
to
process
information
and
data.
A
single
workflow
provides
a
rapid,
consistent
flow
of
information
across
the
system
to
provide
visibility
for
all
stakeholders.
A
If
a
workflow
is
easy
to
follow,
all
generated,
associated
data
is
available
to
all
and
to
establish
accountability.
The
workflow
should
make
it
simple
to
understand
who
did
what
enter
get
left
flow.
Get
left
flow
is
a
simplified
code,
branching
strategy
integrated
with
an
issue
tracking
system
offering
a
simple,
transparent
and
effective
way
to
work
with,
yet
copal
would
get
left
C
ICD
code,
security,
testing
and
monitoring
features.
Get
that
flow
is
a
recommended
best
practice
for
a
developer
workflow,
as
the
graphic
describes
from
left
to
right.
A
A
The
developer
creates
or
changes
code
and
commits
these
changes
to
a
feature
branch
associated
with
a
merge
request,
Yadav,
CI
builds
and
tests.
The
code
peers
reveal
the
code,
discuss
and
suggest
additional
improvements.
If
the
code
is
ready,
one
or
several
team
members
approve
the
changes
and
the
merge
request
is
closed.
A
A
All
coding
efforts
start
with
an
issue
such
as
this
one
entered
by
the
product
owner.
This
request
calls
for
changing
and
improving
the
landing
page
of
a
web
application.
The
landing
page
currently
in
the
production
environment
looks
pretty
ugly
to
begin
work.
A
developer
clicks
on
the
Create
merge
request
button
directly
from
the
issue.
This
creates
a
merge
request
and
a
corresponding
branch
in
the
code.
A
Having
made
some
changes
to
the
code
according
to
the
issue,
the
request
of
them
that
developer
can't
commit
changes
to
a
branch
and
launched
a
pipeline
to
begin
building
and
testing
the
pipeline
can
be
as
simple
or
complex
as
needed.
It
left
CI,
takes
care
of
running
that
pipeline
and
the
different
stages
for
building
testing
reviewing
and
so
on.
A
Certain
individuals
to
the
team
will
have
the
ability
to
approve
changes
made
to
that
code,
so
finally
merge
these
changes
into
our
master
branch
notice
that
also,
as
part
of
the
automation
built
into
the
system
as
part
of
the
get
left
flow.
We're
gonna
close
that
original
business
type
issue
created
by
the
product
owner
with
all
the
audit
trail
with
all
the
signups
and
the
approvals
needed
to
make
sure
that
we
address
the
intent
and,
lastly,
get
lab.
A
So,
very
briefly,
in
this
super
quick
example,
we
reviewed
the
following
get
lap
enables
the
automation
of
redundant
tasks
such
as
creating
a
merge
request
and
kicking
of
CI
CD
pipelines.
A
merge
request
is
used
for
collaboration
during
development,
making
it
simple
for
stakeholders
to
do
code,
reviews
and
work
in
common
items
as
pipelines
build
and
test
code
time
is
reduced
to
process
information
on
build
and
test
results.
A
These
are
made
available
immediately
in
context
of
the
work
common
assets,
such
as
issues,
merge,
requests,
pipelines
and
their
associated
results
provide
this
ability
to
all
project
collaborators
in
a
single
system,
and
events
such
as
code
reviews,
approvals
and
code
merges,
are
recorded
and
unalterable,
establishing
accountability
for
all
that
occurred
in
the
creation
and
delivery
of
code.
I
hope
this
brief
video
was
helpful.
The
following
resources
are
also
available
for
a
deeper
understanding
of
this
simple,
but
powerful
workflow
get
left
flow.