►
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
A
A
It
can
be
quite
difficult
to
enforce
these
coding
guidelines,
so
I've
always
been
promoting
to
have
coding
guidelines
in
the
pipeline,
so
the
pipeline
will
enforce
all
of
the
coding
guidelines.
Usually
the
the
configuration
files
are
these
parts
of
a
repository,
so
it
would
make
sense
to
have
a
central
repository.
You
can
store
any
configuration
file
here
that
will
be
used
for
tools
that
use
in
CI,
so
I've
created
this
example
repository.
A
So
the
idea
is,
if
you
create
one
repository,
that's
or
a
project
called
coding
guidelines
that
the
CI
will
pick
up
all
of
the
config
files
here
and
use
them.
The
goals
of
this
project
are
to
form
a
single
source
of
Truth
for
all
of
the
config
files.
A
So,
instead
of
having
discussions
and
then
have
to
implement
them,
you
can
just
create
a
merge
request
which
it
changes,
discuss
them
and
merge
them,
as
you
like,
very
similar
to
how
most
people
are
already
used
to
working
on
actual
code
and
the
runners
for
your
cicd
will
always
pull
the
latest
configuration
files,
so
in
this
case,
I'm
building
a
image
that
can
be
used
as
a
base
image
for
linters.
A
So
as
an
example,
if
you
were
to
use
coding
guidelines
right
now
with
using
disk
project,
you
can
just
add
this
to
your
CI
CD.
So
you
would
specify
the
image
in
this
case
coding
guidelines
latest.
It
will
always
have
the
latest
files,
and
in
this
case,
since
we
are
only
working
with
python
files,
we
run
flake
8
and
my
Pi,
but
you
can
extend
this
to
whatever
you
want.
A
If
there's
interested
in
making
coding
guidelines
a
a
feature,
I
would
like
to
explore
having
this
configurable
on
a
group
level
or
account
level
and
incorporating
it
is
in
this
into
the
runner.
So
it's
easy
to
run
your
tools
using
the
configuration
files
set
by
your
company.
If
you
have
any
questions
or
suggestions,
please
leave
a
comment
down
below
thanks
for
watching.