►
Description
This is part of an informal demonstration of the process of contributing to NRE Labs (https://nrelabs.io).
For a detailed, authoritative reference, please use the NRE Labs documentation at https://docs.nrelabs.io
NRE Labs Contribution Video Series
- Part 1: First Steps - https://www.youtube.com/watch?v=HOU5k77RQNc
- Part 2: The Antidote CLI - https://www.youtube.com/watch?v=G3sM_5rk2yc
- Part 3: Opening a Pull Request - https://www.youtube.com/watch?v=mfEVoV7FiE0
- Part 4: Previewing Your Changes - https://www.youtube.com/watch?v=c4a2PP4gJqE
A
Hello,
my
name
is
Meadows
well,
and
this
is
part
4
of
our
contributing
to
the
NRI
Labs
curriculum
video
series
and,
in
this
part,
we're
just
going
to
be
taking
a
look
at
previewing,
our
content.
So
in
previous
videos
we
used
the
antidote
CLI
to
bootstrap
a
new
lesson.
Then
we
submit
we
submitted
a
new
pull
request
to
github
to
the
NRI
labs
repository
and
as
part
of
that
pull
request,
we
saw
a
comment
that
said
something
about
a
Content
preview.
A
So
let's
go
check
that
out
so
we're
here
in
the
pull
request
that
we
created
in
the
last
video
and
if
you
scroll
down
to
the
very
bottom,
provided
again
that
all
the
checks
have
passed.
If
they
haven't
passed,
then
this
won't
happen,
but
if
they
have
passed,
if
you
got
a
green
check
box
here
very
soon,
you'll
see
a
comment
by
the
NRI
labs
preview.
Bot,
so
take
a
look
at
the
time
stamp.
Make
sure
it's
a
recent
time
stamp.
This
one
was
seven
minutes
ago.
A
A
That
quick
thing
to
check
is
to
just
see
that
this
commit
ID
is
the
same
as
the
last
commit
that
you
pushed
so
compare
that
to
this
looks
like
that
checks
out
and,
of
course
you
can
always
click
that,
and
it
takes
you
right
to
the
change
where
you
can
see
the
change
we
made
in
the
last
video
where
we
added
this
text.
This
will
be
a
new
lesson
guide,
okay,
cool,
so
that
that's
that
checks
out.
We
have
a
few
tools
for
us.
A
The
very
first
thing
to
check
out
is
this
link
here,
so
I've
constructed
to
preview
your
change
and
it
is
available
here
at
this
link.
I'm
gonna,
middle
click-
this
we
can
open
it
in
a
new
tab.
You'll
see
that
we
have
basically
a
version
of
the
NRA
lab
site.
The
difference
is
just
it's
hosted
at
this
weird
subdomain.
What
this
basically
is
is
a
preview
of
your
pull
request
and
it's
a
live
version
of
the
site
that
you
can
poke
around
with
so
we'll
head
on
over
to
the
lesson.
A
A
A
Now
the
real
question
is:
what
happens
if
something
goes
wrong?
What
do
I
do
to
troubleshoot
if
something
were
to
happen
that
maybe
didn't
get
to
this?
That
didn't.
Allow
me
to
get
to
this
point
where
I'm
actually
able
to
see
things
well,
there's
a
few
tools.
If
we
go
all
the
way
back
to
the
pull
request,
we've
got
a
few
things
to
work
with
the
the
next
line
after
commit
shows
us
logs.
So
if
we
click
that,
basically,
what
this
is
is
a
collection
of
logs
for
some
of
the
back-end
infrastructure.
A
Now
I
want
to
preface
this
by
saying
more
than
likely,
you
won't
need
to
see
this.
It's
it's
likely
that,
if
there's
a
failure,
it
won't
be
here.
This
is
about
this-
is
these
are
really
the
logs
for
spinning
up
the
the
sort
of
the
the
basic
infrastructure
for
running
your
preview
every
once
in
a
while?
A
This
might
present
a
problem,
but
usually
the
kind
of
problems
that
present
themselves
here
will
be
caught
earlier,
using
maybe
some
of
the
CI
checks,
but
nevertheless,
if
this
might
be
a
good
thing
to
peruse,
if
you
feel
like
you'd
like
to
know
more
about,
maybe
the
backend
platform
and
sort
of
how
the
curriculum
was
ingested
during
that
process
feel
free
to
take
a
look
at
this
gist.
The
real
meat
I
think
the
real
useful
tool
is
this
the
the
Jaeger
traces
for
the
lesson.
A
So,
if
you
were
to
click
on
this
inspect
traces
link,
what
that
will
do
is
it'll
open,
a
link
to
this
site,
inspect
preview,
NRI
labs
do,
and
this
provides
you
with
a
lot
frankly,
a
plethora
of
information
on
some
of
the
things
that
year
that
that
you
were
doing
with
the
preview
instance.
So
if
you
clicked
on,
usually
there
will
only
be
one
instance
here,
especially
if
you've
just
loaded
the
preview
will
click
on
the
oldest
one
here.
These
are
basically
interactions
with
the
preview
site
that
was
loaded.
A
So
if
you
click
on
this,
one
you'll
see
a
full
trace
of
effectively
all
the
things
that
took
place
within
the
antidote
platform
to
make
the
lesson
happen.
So,
for
instance,
if
your
lesson,
if
your
lesson
had
an
endpoint
in
it
that
maybe
wasn't
reachable
over
the
network,
you
would
see
that
as
an
error
here.
If,
for
instance,
your
configuration
script
had
a
problem,
you
would
see
that
as
an
error
under
scheduler
configure
stuff,
which
is
the
apt
name,
trace
ID
for
that
or
span
ID,
and
so
yeah.
A
There's
there's
a
few
things
that
you
could
that
you
can
see
here
again,
most
of
the
time
a
maintainer
will
be
here
to
help
you
out
with
this
stuff.
The
reason
this
is
here
is
is
not
for
sort
of
you
to
be
on
the
hook
for
poking
through
all
this
stuff.
It's
mostly
just
to
provide
a
little
bit
of
transparency
so
that
you
and
a
maintainer
can
sort
of
work
together
on
what
the
problem
is.
This
is
a
this
is
by
the
way.
This
is
a
trace.
That
sort
of
indicates
no
problems.
A
Everything
seems
to
be
good
if
there
was
a
problem
that
would
be
some
sort
of
a
red
circle
that
says:
hey,
there's
an
error
here,
since
we
don't
see
that
it
generally
seems
like
everything
happened
pretty
well
and
of
course,
since
we
were
able
to
load
the
lesson,
we
know
that
that's
true,
so
that
is
the
preview
functionality
and
again,
if
you
want
to
add
changes,
let's
say
we
go
into
the
lesson
and
say
you
know
I.
You
know
this
lesson.
Guide
is
kind
of
anemic.