►
From YouTube: Advanced Web IDE
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
Such
that
you're
not
worried
about
how
to
use
the
tool
when
what
you
should
be
worried
about
is
how
to
write
the
great
code
and
that's
part
of
why
these
two
lectures
I've
done
the
previous
web
id
and
this
exists
is
because
knowing
these
basics
and
knowing
these
sort
of
ways
to
navigate,
make
room
in
your
brain
for
the
code
that
you
have
to
write
and
the
things
that
you
have
to
do
as
a
developer.
So
without
further
ado,
let's
get
into
advanced
web
ide
topics.
A
First
off
reintroduction.
To
me
I
don't
know
I
feel
like
I
I
covered
this
already
and
if
you're
in
class,
you
remember,
but
let's
run
down
again
real
quick
pj
matt's.
He
him
I'm
an
education
evangelist
from
florida.
Orlando,
I
love
disney.
I
love
universal.
I
love
theme
parks
in
general,
grew
up.
A
My
dad
worked
at
the
theme
parks,
so
I
had
to
had
to
love
me
some
disney,
I'm
into
poetry,
I'm
technically
a
published
poet,
but
I
don't
like
to
be
like
I'm
a
published
poet
because,
like
it
was
on
a
couple
websites
and
like
a
small
anthology,
I
came
up
in
the
actually.
A
When
I
lived
in
busan,
korea,
I
was
doing
slam
poetry
over
there
with
a
couple
of
other
expats
so
like
that
was
my
thing
for
a
hot
minute:
music,
I'm
a
drummer
by
trade,
but
that's
not
really
true
by
fun.
I
like
to
play
drums
for
fun
and
I'm
a
former
high
school
english
teacher,
that's
what
I
did
for
11
years
before
I
came
to
gitlab.
So
I'm
I
love
education.
I
love
like
teaching
and
working
with
students,
love
80s,
music,
80s
culture,
synthwave
neon.
A
All
that
stuff
is
my
jam
check
me
out
on
twitter,
on
gitlab
and
on
twitch,
and
especially
on
twitch.
We
are
trying
to
host
more
shows
where
we
have
students
come
on
and
talk
about
what
they've
done
on
gitlab
and
projects
that
you're
building.
So
if
you're
interested
in
that,
please
reach
out
to
me
and
we
can
get
you
all
on
twitch
for
a
show.
A
So
what
are
we
covering
today
we're
covering
a
lot
of
different
things,
reviewing
how
we're
covering
how
to
commit
changes
when
we're
talking
about
git
and
how
to
review
those
changes
covering
merge,
requests,
switching,
merge,
requests
and
branches,
we're
covering
something
called
live
preview,
we're
also
covering
how
to
make
a
handbook
page
and
how
to
update
a
handbook
page.
A
The
git
lab
handbook
is
huge.
It's
over
2000
web
pages
large
and
there's
a
ton
of
information
on
there
about
how
we
do
things,
how
you
should
do
things
processes
who
we
are
stuff
like
that,
so
there's
a
very
specific
process
for
creating
a
page
and
updating
one
and
it's
open
to
anyone.
A
Anybody
can
update
a
page
can
edit
a
page
and
make
a
merge
request
if
you
think
there's
something
in
there
that
should
be
in
there
or
if
you
find,
for
instance,
a
typo,
and
you
want
to
fix
one
and
then
finally
we're
going
to
talk
about
how
to
view
ci
logs
directly
from
the
web
ide.
So
what
even,
though,
we're
talking
about
the
web
ide
we're
covering
a
bunch
of
other
things
that
involve
a
little
more
depth
and
a
little
more
work,
so
first
committing
changes.
A
That
gets
essentially
copied
changed
in
some
way
and
those
changes
get
pushed
back
in
and
those
changes
then
reflected
in
the
original
there's
important
keywords.
When
it
comes
to
get
things
you
may
or
may
not
have
heard
of
already
push
pull
commit
branch
merge,
a
push
is
so
there's
think
of
it
to
make
sure
we're
on
the
same
page,
two
things
the
central
repository
exists
and
if
you
want
to
work
on
your
local
machine,
so
the
central
repository
is
on
a
server
somewhere.
A
A
Okay,
let's
keep
talking
about
these
other
things
commit
oh
no
go
back
commit
is
to
it's
sort
of
like
a
a
promise
in
a
way
like
when
you
click
commit
you're,
making
a
promise
that
a
change
has
been
made
right,
but
the
change
isn't
reflected
in
the
repository
until
you
push
to
the
repository
a
branch
when
we
talk
about
git,
we've
got
main
in
some
systems.
It's
called
master,
but
the
main
branch
and
off
of
the
main
branch
right
comes
other
branches.
A
Right
comes
off
like
a
branch
and
then
you're
working
in
that
except
unlike
a
tree,
we
can
push
it
back
into
the
main
source
of
code
and
then
finally
emerge
is
the
act
of
pushing
one
branch
into
the
other
and
making
the
changes
in
that
branch
reflected
in
the
main
one
so
gitlab's
web
ide
makes
it
really
easy
to
work
with
git
a
lot
of
places
you
have
to
work
in
the
terminal
and
you
have
to
like
use
commands
like
get
push,
get
pull
get
remote
get
you
know,
get
fetch
get
there's
so
many,
and
I
there's
a
lot
to
know.
A
A
So
once
you
click
that
button,
I
just
showed
you
it
takes
you
to
this
screen
and
in
this
screen,
as
you
may
remember,
from
the
previous
lecture,
there's
a
space
to
put
what's
called
a
commit
message.
You
can
commit
it
to
the
main
branch
or
you
can
make
a
new
branch
right
here
and
you
can
start
a
new
merge
request
and
what
this
screen
is
really
showing.
You
are
the
changes
that
were
made
or
the
diff
so
on.
A
The
left
is
the
old
file
on
the
right
is
the
new
file,
and
this
is
important
because
it
shows
you
exactly
the
changes
that
were
made
that
are
going
to
be
reflected
in
the
merge
request
that
you're
creating
let's
check
out
creating
a
merge
request.
This
is
the
next
part,
so
you've
clicked
commit
it
takes
you
to
this
previous
page.
A
Then
you
put
your
message
in
you
decide
whether
it's
to
the
main
branch
or
a
new
branch.
You
start
a
new
merge
request
and
click
commit,
and
then
you
get
to
this
page
now.
Excuse
me,
this
page
is
asking
the
person
responsible
for
the
repository
to
change,
something
so,
let's
say
you're
the
owner
of
a
project
and
you've
got
a
friend
who's
working
on
something
and
they're.
Like
hey,
I
solved
that
issue
that
problem
we
were
working
on.
I
made
a
merge
request.
I
need
you
to
check
it
out.
A
Creating
a
merge
request
is
a
signal
to
someone
else
who
has
the
authority
to
merge?
Hey,
I'm
requesting
that
you
put
these
changes
in
now.
You
have
to
give
them
enough
information
about
those
changes,
so
they
can
make
a
good
decision
about
whether
it
should
have
shot
be
merged
and
that's
what
this
description
is
for.
A
A
What
is
changing?
Is
I
deleted
these
three
lines,
but
why
did
you
delete
them?
Okay,
I
added
this
function.
Why
did
you
add
the
function?
I
added
this
function
because
it
increases
the
effectiveness
of
this
code
and
allows
for
it
to
call
on
a
more
important
library
that
we'll
need
later
on
whatever
the
reason
is
give
that
reason,
because
if
you're
just
saying
what
change
was
made,
that's
not
as
helpful.
A
There
are
other
options
here.
You
can
have
a
reviewer,
a
person
who
checks
it
but
doesn't
merge
it.
So
in
some
open
source
projects,
for
instance,
there
might
be
people
who
are
assigned
as
reviewers
and
then
there's
someone
who
can
actually
merge
the
reviewers
have
to
say
yep.
I
looked
at
the
code,
it
looks
good,
there's
no
problems
and
then
the
merge
request,
person
goodness
need
more
coffee,
and
then
the
merger
quest
person
says
okay,
the
reviewers
said
yes,
so
now
I'm
going
to
merge
it
an
assignee
as
well.
A
You
can
see
right
at
the
bottom.
Here
is
sort
of
the
next
person
to
take
action.
So
when
you
assign
someone
the
merge,
request,
you're
saying
it's
your
turn
to
do
something
so
a
good
way
to
do
it
is
assign
it
to
yourself
make
the
merge
request,
make
sure
everything's
correct,
there's
any
pipelines
that
need
to
run
let
it
run,
and
then
you
change
the
assignee.
You
take
yourself
off
as
assignee.
You
assign
the
next
person,
then
you
tag
them
in
the
comments
of
that
merge
request.
A
This
way
they
know
hey
you're,
the
next
person
to
do
something
on
this
all
right.
So
here's
a
demonstration
of
the
whole
process
of
going
from
a
commit
to
a
merger
quest.
So,
first
off
here
we
are
in
my
diva's
live
project.
Again,
I'm
going
to
go
into
my
mariah
carey
based
twitter
bot
and
I
click
that
button
right
there.
Web
ide
or
I
can
hit
the
period
button
that
automatically
opens
it
you'll
see
some
error.
Banners
up
there,
don't
worry
about
those
you'll
see
I'm
already
in
mariah
and
I've
noticed
and
I'll.
A
Let
you
know
what
I
noticed
that
this
line
81
actually
doesn't
do
anything.
I
don't
need
this
in
order
for
my
mariah
carey
twitter
bot
to
function
so
I'm
going
to
get
rid
of
it
gone
notice
that
as
soon
as
I
made
a
change
to
the
file
that
commit
button
over
here
lit
up
it
knows
you
just
made
a
change.
It
knows
you
just
changed
something
in
this
code.
So
if
you
want
to
commit
it,
it
knows,
there's
a
change
there.
A
I
delete
a
few
lines
so
now
it's
only
got
79
lines
and
again
code's
gonna
run
fine,
no
problem,
so
I
click
commit.
It
brings
us
to
this
page
again.
There's
the
diff.
All
this
red
means
deleted
and
notice
that
we're
only
up
to
line
80
now
right,
I
didn't
add
anything
if
you
add
something
it's
in
green,
but
when
you
delete
something
it's
in
red
so
now
I
need
to
fill
out
my
commit
message.
I
need
to
decide
if
I'm
going
to
commit
to
main
or
make
a
new
branch.
A
Now,
in
the
commit
message
you
don't
have
to
say
why
the
commit
message
is
short
and
something
quick
right
removed
extra
line.
81,
that's
not
needed.
I
can
commit
that
right
to
the
main
branch.
If
I
want-
or
I
can
create
a
new
branch
now
notice
that
the
a
few
a
few
options
went
away
when
you
click
commit
to
main
branch,
when
you
click
commit
to
main
branch.
A
No
merge
requests
needed
none
of
that
stuff.
But
when
you
create
a
new
branch,
you
need
to
name
the
new
branch
and
you
have
the
option
to
start
a
new
merge
request
right
then
you
do
not
have
to
start
a
merge
request
right
then,
but
it's
usually
best
practice
to
go
ahead
and
get
that
merge,
request
started,
don't
assign
it
to
anyone.
Yet
merge
request
is
a
request,
so
I
made
my
branch
pj
remove
line
81
I
like
to
throw
my
name
on
my
branches.
A
A
So
a
detailed
description
is
important.
Obviously
you
want
there
to
be
enough
information
there
for
someone
to
make
a
decision,
because
you
are
asking
someone
to
make
a
decision
about
this
project,
not
a
big
deal.
If
it's
just
my
divas
live
project
that
only
I'm
involved
in
but
for
larger
projects.
You
want
to
give
enough
information
here
so
that
the
person
knows
what's
going
on
there.
It
is
I
assign
it
to
myself,
you
can
assign
reviewers
if
you've
got
a
milestone.
A
A
There
we
go
all
right
so
when
we're
talking
about
switching
merge,
requests
and
branches
inside
the
web,
ide
there's
a
little
toggle
that
lets
you
switch
what
merge
equestrian
or
switch
the
branch
that
you're
working
in,
because
if
there's
a
you
know
if
you're
on
main
and
you've
got
a
branch
called
pj
line,
81
right
in
the
web
ide,
if
you're
working
in
main
your
files
are
in
a
certain
state
right.
That
line
hasn't
been
deleted.
Yet,
but
if
you're
on
that
branch
on
the
pj
branch,
the
file
has
been
deleted.
A
So
there
you
have
to
make
sure
you
know
what
branch
you're
working
on
and
if
you've
got
multiple
merge
requests
which
merge,
request
you're
working
in
now
to
switch
there's
a
drop
down
in
the
top
left,
which
I'll
show
you
in
one
second,
but
before
you
leave
the
web
ide.
If
you've
made
changes
or
before
you
leave
the
commit
area,
you
have
to
commit
or
discard
your
changes.
Like.
A
Oh
excuse
me
when
I
talk
a
lot
I
get
yawning,
so
you
have
to
be
like
I'm
committing
this
or
I'm
I'm
not
committing
this
and
I'm
discarding
the
changes
that
I
made
before
you
move
away
from
the
merge
request
page.
A
So
here's
switching
branches,
like
I
said
right
up
here,
we're
inside
a
file
we're
looking
at
different
files
here,
there's
mariah
down
here
and
you
can
go
up
and
you
can
be
like.
Oh,
I
need
to
be
on
pj
remove
and
let's
look
at
that
one
more
time
I
moved
kind
of
fast
there.
So,
as
you
can
see,
I'm
in
main
right
when
I
go
to
that
branch,
it's
going
to
look
different.
A
There
it
is
line,
81
is
still
there
when
you're
on
the
main
branch
up.
There
there's
also
merge
requests.
So
it's
drop
down,
menu
branches,
merge,
requests
over
here
and
you'll,
see
that's
the
name
of
the
merge
request.
If
you've
got
several
merge
requests
that
I'll
have
them
all
here
and
there's
a
search
function
for
them.
A
A
So
this
guy
is
showing
us
an
app
he
has
and
then
on
the
right.
There's
a
little
play
button,
and
this
was
introduced
back
in.
I
think
11
point
something
for
gitlab.
So
when
we're
looking
at
this
you'll
see
over
here
that
little
icon
leads
to
this.
That
is
a
sandbox
that
makes
what
you
have
over
here.
This
project
run,
so
you
can
see
what
it's
going
to
look
like
without
having
to
fully
go
all
the
way
to
actually
deploying
it
somewhere.
A
A
This
doesn't
work
for
all
languages.
It
doesn't
even
work
for
all
project
types,
for
instance,
if
you're
doing
a
non-web
app,
it's
certainly
not
going
to
work.
My
twitter
bots
would
show
nothing
on
this
because
they're
just
code
that
runs
on
a
server
and
activates
stuff
on
twitter,
but
if
you're
doing
something
that
involves
some
front
end,
it
does
it
right
here.
A
So
you'll
see
the
changes
he's
making
are
showing
up
on
the
right
hand,
side
and
let's
go
back
again.
Real
quick,
we'll
see
what
it
used
to
look
like
used
to
be
a
button.
That
said
done,
he's
real,
quick
going
to
add
a
new
file
and
it's
a
done
button
that
he's
creating
and
you'll
see
this
go
from
that
and
he's
gonna
change
it
a
little
bit.
A
A
Let's
pause
there,
we
go
so
as
far
as
creating
a
handbook
page,
it's
kind
of
a
longer
complicated
process.
This
is
like
a
three
minute
video,
but
let's
watch
it
and
go
through
it.
So,
first
off
the
handbook
lives
at
gitlab.com
in
a
project
called
www.
A
A
So
what
you
do
is
you
open
it
up
in
the
ide,
navigate
to
sites
navigate
to
handbook,
navigate
to
source
and
then
to
handbook
one
more
time?
And
then
this
is
a
list
of
all
the
different
sections
of
the
handbook
that
we
have
I'm
gonna
head
to
marketing,
which
is
where
a
lot
of
my
stuff
lives,
because
the
community
relations
team
is
in
marketing,
I'm
heading
down
to
community
relations
and
I'm
heading
down
to
education,
which
is
the
team
that
I'm
on.
A
A
So
I'm
going
to
write
this
file
in
markdown
and
then
when
it
renders
it
will
actually
render,
as
a
new
page
on
the
website,
doing
an
old,
tried
and
true
coding
skill
here,
which
is
copying
and
pasting,
I'm
literally
just
taking
index.html
from
twitch
and
just
pasting
it
here
an
example.
Now
I
don't
want
it
to
be
the
exact
same
page,
so
I'm
going
to
change
the
title
up
top
here
where
we
have
layout
title
and
description.
A
A
A
A
Oh,
that's
done,
click
commit
and
it
would
create
a
new
merge
request
and
in
that
merge
request,
you
say
why
you
need
a
new
handbook
page.
What's
the
purpose?
What's
the
reason
you
notice?
This
is
taking
a
lot
longer
than
my
diva
stuff.
This
is
a
much
larger
project.
It
takes
a
little
bit
of
time
to
gather
up
all
the
things
it
needs.
Additionally,
this
merge
request
has
pipelines
attached
to
it
ci
cd,
so
you
can
see
this
one
comes
with
a
automatic
template
of
stuff.
A
A
And
that's
to
make
a
whole
new
page
in
the
handbook.
If
there's
one
that
already
exists,
you
can
just
click
into
it
in
the
web
id.
So
there's
a
few
ways
to
do
this.
So
let's
take
a
look
here.
This
is
the
twitch
for
evangelist
page.
I
told
you
about
before
and
if
you
want
to
edit
it
if
you're
like.
Oh,
I
found
a
error
here.
I
found
a
misspelling.
I
found
a
dead
link.
A
At
the
bottom
of
every
page,
on
gitlab.com
there's
a
little
thing
there
that
you
can
see
that
says
open
in
web
ide
edit
in
web
id
right
here.
Okay,
when
you
click
that
it
opens
the
web
ide
on
the
index.html.md
page
or
file
for
that
page
there
it
is.
You
find
the
section
that
you
need
to
edit
you
edit
it,
and
then
you
follow
the
same
steps
to
make
a
merge
request,
like
you
did
before.
A
A
Editing,
I
can
spell
I'm
an
english
teacher
and
I
can
spell
I
promise
or
I
used
to
be
an
english
teacher
amazing
and
then
you
would
commit
it
and
you
would
follow
that
same
process
for
merge
requests
like
you
did
before
all
right.
One
of
the
other
things
that
can
be
very
important
is
to
check
the
ci
logs.
A
Now
ci
cd
is
a
more
advanced
topic,
that'll
be
covered
later
on,
but
essentially
it
stands
for
continuous
integration,
continuous
delivery
or
continuous
deployment,
and
it
creates
what
we
call
a
pipeline
and
that
pipeline
outputs,
a
bunch
of
logs
that
allow
you
to
see
the
details
of
the
job
that
ran
so,
for
instance,
I
use
my
ci
cd
to
automatically
update
my
bots.
When
I
make
new
code,
it
automatically
updates
the
heroku
dyno,
where
my
code
is
hosted
and
always
on
to
be
watching
for
bot
activity.
A
A
So
let's
check
this
out
here
we
are
in
the
web
ide.
We
are
inside
of
my
bot
and
click
that
shows
me
a
pipeline,
the
most
recent
pipeline.
I
can
click
directly
into
that,
and
it
takes
me
to
see
all
this
output
that
I
do
not
know
all
what
it
says.
All
I
know
is
at
the
end,
the
twitter
bot
works
and
it's
basically
magic.
A
So
all
of
our
docs,
like
I
said
they
were
linked
in
the
previous
presentation
but
they're
at
docs.gitlab.com,
backslash
e
e,
slash
user,
slash
project
slash
web
underscore.
I
don't
know
why.
I'm
reading
the
whole
thing
it's
here
on
the
screen
for
y'all
and
I'm
gonna
make
it
a
link.
A
So
that's
all
there
for
you,
everything
you
need
to
know
about
the
web
ide
available
on
our
docs,
how
to
use
it.
What
to
do?
I
hope
you
all
enjoyed
this.
I
hope
it
was
the
most
fun
you've
literally
ever
had
in
your
entire
life,
and
I
hope
you
guys
continue
to
do
well.
If
you
have
any
questions
again,
reach
out
to
me
on
twitter,
find
me
on
gitlab
start
an
issue
and
make
me
the
assignee.
So
we
can
have
a
chat,
but
thanks
very
much
and
have
a
good
one.