►
From YouTube: Tips & Tricks: Gotta Git Them All - GitHub Universe 2016
Description
It's the little details that make using Git and GitHub so great, but what are those details and commands that expose you to the best of the platform? Do you know how to close issues from pull requests? How to quickly browse to a file? Do you know how to find the history of a range of lines in a given file? Join Jamie Strusz and Brent Beer from GitHub to answer these questions and find joy in the little things.
About GitHub Universe:
GitHub Universe is a two-day conference dedicated to the creativity and curiosity of the largest software community in the world. Sessions cover topics from team culture to open source software across industries and technologies.
For more information on GitHub Universe, check the website:
https://githubuniverse.com
B
A
B
And
also
as
a
follow-up
to
this,
if
there's
any
questions,
because
this
is
going
to
be
kind
of
quick
to
run
through
some
of
these
we're
gonna
be
at
the
at
services
booth
after
this
doing
some
office
hours.
So
if
there's
any
questions,
anyone
wants
to
come
by
now
additional
follow-ups,
we
can
do
that
there
I'll
talk
about,
can.
A
Okay,
I'll
take
the
right
into
the
mic;
I
don't
know,
I'll
double
make
it
sorry,
I'm
Jamie
I'm,
a
services
engineering
based
out
of
Seattle
I
like
art
and
I,
sometimes
live
in
a
van
with
my
boyfriend
and
dog
you're
welcome,
so
the
agenda.
For
today
it's
going
to
be
really
quick,
like
I
said
we're
going
over
some
get
get
LFS,
github,
just
and
Adams
so
buckle
your
seatbelts
put
your
trays
in
the
upright
position.
Here
we
go
so
get
we're
going
to
talk
about
some
workflow
efficiencies,
some
advanced
usage
and
get
LFS.
B
I
think
this
is
one
of
the
interesting
parts
about
it
is
that
for
as
long
as
you
can
be
working
with
it,
there's
always
going
to
be
new
and
interesting
command-line
options
or
use
cases
that
you
can
find
with
any
commands.
Even
the
simple
commands
that
you
use
every
day
like
get
log,
this
is
one
that
I
discovered
while
talking
to
some
customers.
They
wanted
some
some
solutions
for
some
finding
who's
changed
a
file
between
a
start
and
end
point,
and
they
wanted
to
see
all
the
commits
that
involved
those
pieces.
B
So
with
this
you
can
say,
git,
log,
L
or
the
capital
L,
give
it
a
start
and
end
and
then
a
colon
for
the
file.
So
it
basically
looks
a
little
bit
like
this
when
you're
inside
your
repository
on
your
command
line,
git
log
I
need
from
the
third
line
down
to
the
tenth
line,
find
give
me
all
of
the
commits
that
have
edited
those
lines.
This
could
be
interesting
for
in
case
you
want
to
you're
refactoring
some
method,
and
you
need
to
find
out
who
edited
it
last
or
how
it's
evolved
over
time.
A
You'll
have
noticed
that
there
were
different
colors,
so
one
of
the
things
that
we
want
to
make
sure
everybody
is
aware
of.
If
you're
not
already
is
you
can
actually
configure
the
colors
within
get
you
can
either
do
the
command
that
we
have
here,
which
is
just
like
an
auto
colorization
or
in
your
actual
config
file.
You
can
go
in
and
specify
which
colors
you
want
and
it
is
capable
of
doing
actual
color
names,
it's
capable
of
doing
ans,
I
and
some
are
capable
of
doing
RGB
as
well.
Yeah.
B
A
A
So
next
we
have
get
status
status,
SB
trying
to
conform.
My
words
into
one
there,
and
so
here
the
S
stands
for
short
and
the
B
is
for
branch.
So
normally,
when
you
do
this,
it's
going
to
put
out
the
short
format
and
it's
also
still
going
to
maintain
that
branch
name.
So
it's
not
lost
and
it's
going
to
look
a
bit
like
this.
So
before
we
have
five
lines
of
code,
you
see
the
branch
name,
it
doesn't
necessarily
stand
out
the
way
that
it
does
in
the
after
that's
shown,
and
then
also
you
see.
B
A
It's
very
clean,
and
so
again
you
can
kind
of
specify
how
your
get
log
appears
just
to
make
it
prettier
more
readable.
It's
kind
of
a
nice
thing
to
do,
especially
if
you're
staring
at
lines
of
code
all
day.
I
know
most
of
us
in
this
room
have
had
those
days.
So
here
we've
chosen
the
graph
option
to
branch
to
show
like
a
branch
graph
and
then
also
we're
specifying
colors
and
I
mentioned
before
you
can
use
color
names.
This
is
what
we've
done
here.
A
The
a
b
b
re
v
dash
commit
is
to
abbreviate
and
it
just
shortens
the
length
and
then
the
date
relative
is
something
that
you
can
do
for
something
that
is
relative
to
the
current
time
that
you're
actually
putting
the
command
in.
So
it
could
be
like
three
hours
ago,
six
days
ago,
nine
weeks
ago,
relative
to
now
when
you're
actually
putting
that
command
in,
and
this
is
a
mouthful
to
type
so
we
definitely
suggest
making
an
alias
for
the
phone.
If
this
is
something
that
you
want
to
use
for.
B
A
I
mean
unless
you
want
to
but
you're
in
the
minority
there.
So
this
is
an
example
of
how
that
looks,
and
it's
super
pretty
and
you
can
see
the
branch
and
kind
of
like
an
ASCII
art
format
which
I'm
a
pretty
big
fan
of.
I
think
that's
super
awesome,
so
yeah,
that's
what
that
looks
like
you
can
see.
Each
component
has
a
different
color
and
it's
just
easy
to
find
exactly
what
you're
looking
for
and
it
saves
you
time
and
I
strain.
B
So
geek
rep
is
kind
of
an
interesting
command
because
I
was
talking
to
some
house
colleagues-
and
we
use
this
before
when
we
are
looking
for
a
certain
phrase
or
some
changes
within
a
file
or
sorryi
method
within
some
file
and
finding
out
where
it
is,
if
it's
called
in
other
places,
but
get
grep
itself
is
actually
a
little
bit
more
advanced
than
that,
and
actually
just
straight
off
from
the
man
page
at
the
very
bottom.
They
list
an
example
about
this
about
finding
a
method
called
time.
B
T
what's
interesting
about
this,
is
you
can
you
can
ask
grep
to
look
for
this
and
find
all
files?
So
you
have
the
file
separator
there
and
you're
using
a
little
bit
of
the
regular
expressions
to
say,
find
where
this
is
mentioned
in
any
file
so
long
as
that
file
has
a
file
extension
of
C
or
H.
So
this
is
a
C
application
and
we're
looking
for
the
C
files
or
the
H
files,
where
this
method
is
actually
called.
B
So
if
you
need
to
do
some
code
refactor-
and
you
need
to
find
where
this
this
method
is
actually
called
from-
this
is
a
really
good
command
actually
used.
If
you
don't
have
a
good
global
search
within
a
text
editor
or
anything
like
that
or
if
you're
already
on
the
command
line,
having
an
option
like
this
that
you
can
quickly
type
to
stay
in,
that
context
is
pretty
important.
It's
also
very
neat.
A
So
this
is
another
great
one
that
I
like
get
config
global
help,
autocorrect
I'm,
definitely
guilty
of
typing
Co
m.I.t
instead
of
comm
ITV
can
sometimes
my
fingers
move
faster
or
slower
than
my
brain
and
it
autocorrect
something,
and
it
points
out
when
you
do
a
miss
type
like
that,
and
in
this
case
we
actually
have
it
set
to
auto
correct
for
you
and
a
big
heads
up
here.
Yes,.
B
So
if
you're
typing
a
command
like
get
commit
and
you
miss
type
it,
this
is
what
the
suggestion
is
going
to
do.
Instead
of,
if
you
don't
have
this
enabled
it'll
say:
did
you
mean
to
type
git
commit
and
it
just
waits
for
you
to
retype
it?
If
you
turn
on
auto
the
autocorrect
here,
and
you
give
it
that
second
as
the
tense
in
this
case
as
that
time
period,
that
means
it'll
wait
that
long
before
it
actually
execute
that
command.
B
So
weird,
a
caution
on
this,
if
you
know
it
thinks
you're
trying
to
do
a
reset
hard
and
you
erase
all
your
work
because
you
have
auto
complete
or
autocorrect
turned
on,
you
know
maybe
play
around
with
that
a
little
bit.
Maybe
you
know
if
it's
ten
seconds
you're
already
gonna
be
able
to
type
something
faster
than
that
so
somewhere
between
one
and
ten
seconds,
wherever
you
feel
comfortable
with
that
definitely
a
word
of
caution,
but
it
is
an
interesting
fix
if
you
mistyped,
something
correctly
all
right,
miss
type,
something
all
the
time.
A
A
Lightning
round
so
here
we
have
get
ad
P
P
stands
for
patch
mode
in
this
case,
and
patch
mode
is
excellent.
We
highly
recommend
it.
Basically,
it
allows
you
to
stage
only
portions
of
files,
so
you're
not
actually
having
to
go
through
and
commit
the
entire
file
just
parts
of
it
that
were
actually
changed.
So
your
can.
Your
commits
are
more
concise
and
everything's
going
to
process
a
lot
faster.
Is
it
appropriate
to
use
all
the
time?
A
B
I
think
I
use
this
almost
every
single
time,
because
I
want
my
commits
to
be
very
small
pieces.
This
saves
me
from
very
large
merge
conflicts
in
the
future,
because
I
have
this
granular
commits.
Also,
if
I
bug
statements
are
hard
coded
environment
variables
in
my
code-
and
I
don't
want
to
commit
those
yet,
but
I
want
to
commit
something
else.
Get
add
p.
Give
me
this
interactive
mode
of
selecting
which
piece
of
the
code
actually
want
to
commit.
B
B
B
So
how
many
times
does
anyone
worked
with
a
merge
and
it's
popped
open
your
default
text
editor
and
you've,
not
edited
the
text
at
all
and
you
just
save
it,
and
it's
kind
of
a
hiccup
in
your
workflow
just
show
of
hands
real,
quick,
okay
so
like
for
me,
every
almost
every
single
time,
unless
it's
a
fast-forward,
merge
I
did
discover
about
the
no
edit
flag
which
isn't
just
on
merges.
You
can
also
do
this
on
git
commit
dash,
amend.
B
If
you
need
to
amend
to
commit
you,
don't
you
can
just
reuse
the
commit
message
by
saying
no
edit,
you
could
also
again
thinking
back
to
those
aliases.
You
could
set
an
alias
for
this,
so
instead
of
saying
get
merged,
if
you
just
said
get
ng
or
something
similar,
whatever
might
work
for
you
just
to
reuse
that
commit
message
every
time.
This
is
a
really
good
one
to
use
to
kind
of
work
into
your
workflow
in
rebase.
How
many
people
feel
comfortable
using
rebase
every
day.
A
B
Double
comfort
there
rebase.
I
is
one
of
those
interesting
next
steps
to
understanding
how
rebase
works.
I'm,
not
just
changing
the
base
of
my
branch
for
a
better
merge
later,
but
I
want
to
control
how
that
work.
I
just
did
is
actually
stored
in
history.
So
three
base
I
is
gonna.
Put
me
in
this
interactive
mode,
that's
what
the
I
stands
for,
and
it
allows
me
to
look
at
a
recipe
of
my
work
to
decide.
Well,
maybe
I
wanted
to
reword
this
commit
message
or
I
wanted
to
edit
the
actual
dip.
B
The
actual
change
to
this
file
that
I
was
working
on
or
maybe
there's
a
commit
in
the
last
five
that
I
actually
don't
want
to
be
in
history
at
all.
Well,
while
doing
interactive
mode
in
specifying
some
point
in
time
like
five
commits
from
head
ago
or
specifying
an
individual
commit
to
actually
go
back
to
or
get
rebase
I
origin
/
master
before
I
push
my
it's
to
anyone
else.
This
allows
me
to
control
the
commits
and
how
they'll
be
viewed
by
other
people.
B
So
the
main
thing
I
want
to
stress
here
is,
as
we
do
interactive
mode,
be
cautious
that
we
are
rewriting
those
commits
in
history.
So
this
is
something
you
really
want
to
only
get
used
to
before.
You've
pushed
any
of
your
changes
so
once
you've
pushed
them
to
github
and
other
people
have
seen
them
doing
interactive
mode
to
rewrite
that
history
is
going
to
cause
some
trouble
down
the
line
for
them,
potentially
that
your
co-workers
or
your
colleagues
or
anyone
else,
you're
collaborating
with.
So
please,
please,
please.
B
A
B
So
in
this
scenario,
I
say
git
rebase
I
five
commits
ago,
and
it
pulls
open
Adam,
which
happens.
Man
happens
to
be
my
default
text
editor
and
for
that
very
first
commit
that's
the
one
I'm
selecting
I
want
to
reword.
The
second
commit
message:
I
want
to
edit
the
the
third
one
to
add
some
additional
context
to
it
and
I'm
then
gonna
squash,
the
fourth
one
into
the
third
one
and
then
I'm,
just
gonna
select
the
last
one.
One
thing
I
could
do
here
is
delete
a
line.
B
I
know
at
the
very
bottom
of
this
list.
It
says
d4
drop,
which
is
a
newer
action
that
you
can
take
within
newer
versions
of
git,
but
you
could
also
just
delete
an
entire
line
there.
Another
thing
that
people
get
caught
up
with
with
this
is
editing
that
commit
message
that
won't
actually
do
anything,
those
that
commit
ID
and
the
commit
message.
There
is
simply
reference
for
you,
so
you
know
what
those
commits
are
without
having
to
dive
into
them.
So
this
is
another.
B
If
you're
ever
working
on
a
series
of
feature
changes-
and
you
made
one
change
and
then
maybe
five
commits
later,
you
decided
that
there
was
something
you
wish
was
in
that
last
commit
when
you'd
make
that
new
change
in
that
commit
message.
You
can
say
squash,
exclamation
point
or
squash
bang
and
then
a
similar
commit
message
and
then
just
continue
on
working
and
later,
when
you
do
a
rebase.
If
you
include
the
squash
option,
when
you
go
into
that
interactive
mode,
it'll
sort
your
commits
for
you,
so
that
it's
already
set
up
to
be
squashed.
B
B
Any
use
cases
anyone
put
their
presentations
up
on
github
with
LFS.
All
my
talks
are
open
source
on
github
with
LFS,
so
so
so
LFS.
If
anyone
doesn't
actually
know,
stands
for
large
file
storage.
So
this
is
an
open
source
project
that
you
can
download
and
use
on
your
laptop,
and
you
can
configure
to
be
on
get
up.
Github
comm
for
your
account
or
get
up
enterprise
and
what's
gonna
happen
here,
just
like
we
have
in
this.
B
This
little
graphic
is,
if
you
have
those
binary
files
that
are
not
really
good
to
version,
but
you
need
to
have
along
the
source
code,
anyways,
so
game
design,
as
you
have
those
really
large
assets
that
as
a
developer,
I
don't
actually
need
to
use
but
needs
to
be
in
the
source
code.
I
don't
want
it
to
take
up
a
large
amount
of
space
in
my
source
code,
because
over
time
that
just
makes
my
repository
very
large
I
want
to
store
it
in
some
kind
of
external
storage.
B
A
B
This
is
one
of
those
commands
that
it's
going
to
help
that
workflow
a
little
bit
so
get
LFS
prune.
This
is
going
to
delete
local
copies
of
the
LFS
files,
which
old,
which
will
free
up
disk
space
on
your
local
git
repository.
So
this
is
something
you
would
run
on
your
laptop
if
your
local
git
repo
was
getting
pretty
large
because
you
had
additional
copies
of
those
large
assets
over
time
that
you
just
didn't
need
anymore.
B
It's
a
really
good
command
to
run,
and
maybe
even
a
little
bit
better
is
to
pass
in
the
see
option.
This
will
go
and
check
the
server
to
see
that
those
copies
exist
there.
So
you
can
delete
it
locally
and
it'll
still
be
on
the
server
for
you
to
actually
use
so
a
pretty
good
efficiency.
There
there's
a
whole
bunch
of
configuration
options
you
can
set
for
LFS.
B
You
can
either
pass
them
in
on
the
command
line
or
you
can
set
these
configuration
options
and
also
a
point
to
note
here
is
that
I'm
not
saying
get
config
global.
It's
a
git
config
for
that
local
repository,
because
on
a
per
repository
basis,
I
may
want
to
exclude
different
files.
So
here
in
this
project,
there's
files
that
are
inside
the
media
directory-
maybe
one
that's
called
really
big
files-
that
I
don't
need
all
the
time
and
I
will
never
need
it.
B
B
Also
there's
the
inverse
of
this
so
LFS
dot
fetch
includes,
because
you
want
to
make
sure
you
always
include
a
certain
file
and
I
just
want
to
give
a
shout-out
to
Rick,
Olson
or
techno
weenie
and
Taylor,
Blau
or
Atty
Taylor
are
who
work
on
the
git
LFS
project
at
github.
They
were
telling
me
about
LFS
clone,
which
I
think
is
a
really
interesting
command
as
well.
B
Two
operations
and
kind
of
in
parallel
does
a
regular
git
clone
that
only
gets
the
Pointer
files,
so
not
the
large
assets,
but
the
pointers
to
them,
and
then
it
does
a
get
LFS
check
out
which
resolves
those
pointers
in
parallel.
The
TLDR
of
this
is
it
just
works
faster.
So
it's
a
lot
faster
to
use
this.
If
you
know
you're
working
with
an
LFS
repository
just
run,
get
LFS
clone.
B
B
Hopefully
after
today,
everyone
will
raise
their
hand
in
the
next
talk
that
you
see
this.
So
people
make
jokes,
they
say
SVN
hub
instead
of
github,
but
with
this
you
know,
I,
don't
know
necessarily
why
you
would
maybe
do
this,
but
it
works
just
like
in
SVN
repository
for
you
to
work
with.
This
is
pretty
good
for
people
transitioning
over
to
get
in
github
if
they
have
some
some
worry
about
git
in
the
workflow,
and
they
just
want
to
keep
using
SVN
as
a
temporary
measure,
then
later
transition
over
to
using
git.
B
This
is
a
really
good
way
to
convince
them
to
get
over
into
github,
to
actually
use
that
so
again,
not
a
permanent
solution,
but
it
does
work
and
if
you
have,
people
who
are
hesitant
about
github,
definitely
encourage
them
to
look
at
this
and
then
later
do
some
migration
work,
maybe
even
coming
over
to
the
services
desk.
Later
and
talking
to
us
about
migrations,
I'll
help
you
out
with
that
too.
Definitely.
A
A
Basically,
it's
going
to
set
you
up
with
an
email
digests
and
you
can
choose
how
often
you
want
to
receive
this
email
digest,
but
basically
it's
going
to
give
you
a
summary
of
things
that
are
trending
on
github
and,
more
importantly,
you
get
information
about
people.
You
follow
whichever
repositories,
they're
starring
so,
for
instance,
a
good
use
case
for
this.
If
you're
getting
started
an
open
source
and
you're
trying
to
figure
out,
ok
so
which
open
source
projects
can
I
start
contributing
to
I'm
a
little
hesitant
I'm,
a
little
scared.
A
You
know
I'm
just
dipping
my
toes.
If
you
find
people
to
follow
and
they
start
starring
other
repositories,
chances
are
they're
going
to
star
repository
that
you
would
be
interested
in
contributing
to
and
there's
other
use
cases
for
this
as
well,
but
that's
definitely
something
that
I've
talked
to
several
people
about
already.
So
this
is
an
example
of
what
that
looks
like
you
can
see.
You
can
choose
like
a
daily
digest,
weekly
or
monthly
and
again
trending
repositories
on
github
and
then
things
from
people
you
follow
whatever
they're
starring.
Alright.
B
So
it's
a
good
learning
experience
for
new
people
as
they're
working
and
learning
about
repositories
on
github
discovering
some
new
language.
You
find
out
those
talks
from
people
here
at
github
and
you
want
to
go,
follow
those
people
on
github
and
find
out
what
other
projects
they're
being
interested
in
and
starring
as
well,
and
this
is
kind
of
an
interesting
little
thing
that
just
came
out
a
couple
I
think
a
couple
weeks
ago
or
a
couple
days
ago,
on
github
as
well,
better
collaboration
with
Forks,
so
there's
been
times
I.
B
Think
actually
one
of
my
first
pull
requests
I
submitted
to
a
project.
They
told
me
that
the
only
way
they
could
accept
my
pull
request
was,
if
I
reject
it
or
if
I
removed.
One
of
the
commits
from
that
that
whole
series
of
that
whole
branch
that
I
was
working
on
I
didn't
know
how
to
use
rebase
at
the
time.
So
I
had
to
look
it
up.
B
It
took
me
a
long
time
by
turning
this
on,
for
the
pull
request
that
you're
sending
to
maintain
errs,
there's
a
little
setting
in
the
lower
right
hand,
corner
of
those
pull
requests
that
will
essentially
say
I'm.
Okay,
with
that
maintainer
push
directly
to
my
branch
on
my
fork.
So
if
there's
some
little
intricate
workflow
that
they
have
going
on
and
they
suggest
something
to
you,
you
don't
know
how
to
do
it
turn
this
on
and
they
can
push
to
the
your
branch
and
then
they
can
accept
your
pull
requests.
B
A
B
So
Paul
Betts
was
working
on
this
repository
called
reactive
UI,
just
some
open
source
project.
The
reason
why
I
always
like
to
show
this
is
because,
in
his
release
notes
he
has
this
little
markdown
header
that
says
what's
new
and
inside
that
header
he's
actually
doing.
The
custom
ranges
on
that.
So
if
anyone
was
to
find
out
what's
changed
between
different
releases,
he's
able
you're
able
to
click
that
link-
and
it
brings
up
that
URL
for
you.
You'll-
also
see
this
as
you
go
to
pull
requests
where
people
have
made
some
additional
edits.
B
A
B
Yeah
so
you're
able
to
click
those
line
numbers
when
you're
on
that
file
itself
to
actually
give
people
the
context
to
what
you
actually
want
them
to
look
at.
So
if
you're
gonna
ask
someone
to
take
time
out
of
their
day
to
look
at
some
method
or
you
want
to
have
a
discussion
with
someone
and
you
want
to
get
them
exact
context
to
what
that
is.
You're
talking
about,
don't
just
say
the
file,
don't
just
say
the
method
name
actually
get
these
anchor
points
for
them
to
actually
look
at.
B
A
They'll
have
no
excuse
to
avoid
your
request,
and
so
this
is
cool.
Not
many
people
know
about
it,
but
we
use
it
all
the
time
within
github
and
it's
referencing
and
closing
issues
and
pull
requests.
Actually
in
your
comment.
So
whenever
you
do
a
commit
message
or
like
close
something
and
use
the
word
fix,
fixes
fixed
clothes
closes
closed,
resolve
resolves
resolved
those
kind
of
iterations,
and
you
also
include
the
issue
number
the
pull
request.
It
will
actually
commit
that
and
close
the
other
item
that
you
just
cross-referenced.
A
B
Interesting
about
this,
too,
is,
as
you
work
in
these
repositories,
with
issues
that
end
up
in
the
thousands
of
numbers
or
pull
requests
within
the
thousands.
It's
really
hard
to
remember
the
exact
number
of
a
pull
requests.
You
were
at
or
exactly
issue
you're
at.
But
if
you
can
remember,
remember
the
title,
you
can
start
typing
the
title
as
you
want
to
autocomplete
this
as
well,
so
you
can
either
close
those
issues
or
pull
requests
from
commit
messages.
B
Maybe
if
you
have
a
rebase
workflow
and
you
want
it
to
reword
one
of
those
commit
messages
to
close
an
issue
or
another
pull
request
or
when
you're
actually
sending
a
pull
request
or
pull
request
like
we
are
here
in
that
comment
box.
Just
like
any
other
comment
box
on
github.
This
will
do
the
auto
completion
or
the
suggestion
of
other
issues
and
pull
requests
for
you
to
work
with.
So
don't
worry
about
remembering
numbers.
B
A
B
B
You
see
some
of
this
with
the
UI
when
you
start
doing
assignee
and
labels
and
milestones
and
mentions,
and
things
like
that,
but
this
one's
interesting,
because
if
you
wanted
to
review
or
do
a
triage
of
issues
and
pull
requests
on
your
project,
you
can
sort
by
ones
that
are
at
least
passing
every
CI
status.
So
if
you
turned
on
Travis
CI,
does
it
free
on
your
project
and
you
have
a
lot
of
pull
requests
to
work
with
you
can
easily
sort
and
find
the
ones
that
are
at
least
passing
CI.
B
So
we
can
see
a
little
bit
with
the
UI
here.
Just
typing
in
the
upper
right
hand
corner
sorting
those
out
for
us-
and
this
is
one
of
my
favorite
pieces
of
github
I,
feel,
like
some
people
know
about
search
and
they
do
a
little
bit
of
searching,
but
they
don't
use
any
of
the
advanced
search
queries
similar
to
maybe
Gmail
searching.
You
can
add
in
that
you're.
Looking
for
just
an
issue,
you're
looking
for
a
query
within
a
title,
you
want
to
scope,
it
do
only
a
repository
or
only
within
an
organization
account
there's.
B
So
many
different
things
to
do
within
code
search.
Our
help.
Documentation
on
this
is
pretty
phenomenal.
I
constantly
reference
it
because
I
don't
have
it
all
memorized
myself,
but
it's
pretty
awesome
to
see,
for
instance,
just
searching
on
github
globally
for
a
repository
github
slash,
get
LFS
I'm
looking
for
something
that
is
a
pull
request
and
it
has
locking
in
the
title
so
it
kind
of
reads
a
little
bit
like
English
or
if
you're
used
to
Gmail
searching.
B
This
is
where
I
see
most
people
making
the
connections
here,
which
makes
it
really
easy
to
find
open
source
projects
open
source,
repos
issues,
whatever
it
might
be
or
within
your
enterprise,
especially
as
you
start
reaching
hundreds
or
tens
of
thousands
of
people.
You
never
know
what
else
anyone's
were
hang
on
and
you
need
to
find
those
other
pull
requests
to
learn
from
those
conversations.
B
A
Many
of
you
include
code
blocks
within
like
a
markdown
file
or
something
how
many
of
you
use
syntax
highlighting
in
those
code
blocks
pretty
good
number.
We
just
like
to
point
this
out
because
it's
very
great
for
documentation
purposes
you
can
see
here.
This
is
going
to
be
highlighted
according
to
how
you
might
see
it
in
your
actual
text
editor.
So
it
just.
It
looks
a
lot
nicer
than
just
being
your
black
text.
A
This
is
a
good
one
keyboard
shortcuts
any
page
on
github
com.
You
can
do
the
question
mark
and
it
will
bring
up
the
shortcuts
that
are
available
for
any
given
page.
Some
of
those
that
we
like
are
the
W.
It
brings
up
the
branch
selector.
The
L
will
bring
up
the
labels
on
existing
issues.
The
S
will
focus
on
the
search
field
and
then
Brent
husband,
yeah.
B
So
how
many
people
use
the
T
key
to
search
for
files?
Okay,
so
there's
a
lot
of
good
uses
of
a
lot
of
experience,
people
in
the
room.
So
that's
that's
pretty
good.
There
is
a
button
for
this
when
you're
on
the
code,
tab
of
a
repository
but
I
still
just
remember
the
T
key
every
time.
I
think
that's
that's
used
in
some
other
places
as
well.
B
Searching
for
those
files
is
also
going
to
be
a
fuzzy
search,
so
that
means
I,
don't
have
to
remember
the
full
path
or
where
that
file
is,
but
might
remember
that
it's
some
command
with
a
go
extension
on
the
file
name
or
it's
called
clone.
It
does
a
fuzzy
match
on
the
file,
so
it
makes
it
really
easy
to
actually
find
it.
A
B
Still
there,
but
you
just
you,
won't
see
it
in
the
UI
because
just
by
default
are
meant
to
be
very
lightweight
repositories,
but
you
can
still
push
additional
branches
to
your
gist.
You
just
won't
see
them
so
I
sometimes
use
this.
If
I
want
to
work
on
something
for
review
and
then
merge
it
in
a
master
and
push
it
up
to
the
gist
for
everyone
to
see.
Yeah.
A
B
If
you're
using
github
pages-
and
you
want
it
to
show
good
code
samples
that
live
on
in
gist
or
you're,
writing
a
blog
and
you
wanted
to
embed
gist
within
your
blog
and
just
plain
HTML,
you
can
link
out
to
that.
That's
just
source
with
the
P
IPB
extension
at
the
end.
To
actually
render
that
gist.
So
it
looks
actually
beautiful
on
your
blog
yeah.
B
So
this
is
a
really
interesting
one
when
you're
working
in
atom.
It
took
me
a
little
while
to
see
this,
because
it's
really
subtle.
On
the
the
left
hand,
side
by
the
file
numbers
as
we
start,
editing,
different
text
or
deleting
text
or
adding
new
lines
or
whatever
it
is
atom,
is
actually
get
aware.
So
it
knows
that
I'm
making
these
edits
and
it
adds
a
little
bit
of
a
marker
next
to
those
file
numbers
as
we
go
through
them.
B
If
you
want
to
review
what
it
is
and
you're
not
using
get
at
P
or
you're,
just
you
want
to
stay
in
your
text
editor.
You
can
hit
alt
G,
take
your
hands
off
the
keyboard
and
then
hit
the
up
key
or
Alt
key
and
then
hit
the
down
arrow.
You
can
switch
between
these
edited
lines
within
the
current
file,
you're
working
on
so,
if
you're
working
on
a
very
large
massive
file-
and
you
want
to
find
out
where
these
changes
are
toggle
through
them
really
quickly
with
these
keyboard,
shortcuts
I
think
is
good.
B
Alt
G
is
kind
of
everything
involving
it
and
it
might
be
hard
to
remember
that
because
I
don't
remember
all
the
keyboard
shortcuts
of
Adam
but
the
one.
If
there's
one
keyboard
shortcut
of
Adam,
you
must
remember
today
it's
command
shift
P.
This
will
bring
up
the
command
palette,
which
is
incredible,
awesome
tool
for
allowing
you
to
find
all
the
other
packages
that
you're
working
with
you
installed
a
git
plug-in
or
a
git
package,
and
you
can't
remember
all
the
key
bindings
for
it.
B
You
can
solve
a
markdown,
rendering
tool,
merge,
conflict
tool
of
markdown
to
PDF
package,
which
all
of
those
three
will
will
show
here
in
a
minute,
and
but
you
can't
remember
the
keyboard
shortcuts,
for
it
type
man
shift
key
and
then
type
git
or
markdown
or
PDF
or
pain,
or
anything
like
that,
and
you
will
actually
find
these
different
commands
to
kind
of
increase
your
own
workflow
there,
and
this
is
one
of
those.
This
is
the
markdown
preview
one.
So
you
can
actually
toggle
the
way
it's
rendering
the
markdown
here.
B
I
usually
have
it
set
to
the
showing
it
the
exact
same
way,
it'll
be
on
github,
because
this
is
the
markdown
file.
I'm
gonna,
push
it
to
github
anyways,
so
before
I
push
it
I
want
to
make
sure
it
renders
correctly.
I
usually
have
problems
with
the
headers
and
some
bullet
bulleted
items,
after
that
it
sometimes
renders
a
little
differently.
So
I
can
preview
that
right
before
I
end
up
pushing
it
up
to
the
server,
which
is
pretty
cool,
and
that's.
A
A
good
use
case
for
people
who
are
not
necessarily
developers
to
kind
of
get
into
markdown
and
put
their
documentation
up
on
github,
so
people
that
actually
work
on
documentation
or,
for
instance,
at
github
every
department
is
on
github
and
uses
github.
So,
even
if
you
don't
have
that
background,
it
makes
it
easier
for
you
to
learn
it
and.
B
This
one's
kind
of
a
life-changing
one
for
me,
so
it's
a
merge,
conflict
resolution
package
inside
Adam.
This
is
awesome
because
it
actually
I'm
sorry
if
it's
a
little
hard
to
see,
but
it
actually
adds
the
highlighting
around
the
where
the
conflict
is
another
very
bottom
of
the
screen.
It's
also
going
to
mention
how
many
more
conflicts
are
in
that
file
and
that
progress
bar
on
the
lower
right
hand
corner,
and
it
also
lists
every
single
conflict
within
your
package
that
you
have
to
go
to
next.
B
B
And
and
finally,
with
this
one
what's
interesting
about
this-
is
this:
is
that
markdown
PDF
one
that
Chris
talked
about
in
his
keynote?
If
I
can't
remember
what
the
keyboard
shortcut
to
do,
this
is
open
up
command,
palette,
search,
PDF,
converts
that
markdown
file
to
a
PDF
and,
of
course,
I,
can
go
open
that
up
in
finder
or
your
Explorer
window
and
then
open
up
that
PDF.
B
B
One
last
thing
here:
I
thought
was
really
interesting-
was
the
the
time
machine
package
that
Chris
talked
about.
So,
if
you're
working
on
a
particular
file-
and
you
want
to
know
the
history
of
that
file-
and
you
want
to
compare
it
to
other
versions-
you
can
turn
on
get
Time,
Machine
and
actually
look
back
in
time
and
how
that
file
has
changed
and
see
the
differences,
which
also
do
some
of
that
highlighting
I
think
this
is
fantastic.