►
Description
Presented by Shanku Niyogi, SVP of Product, GitHub
This demo-packed session will show you how to build for the global market using the latest tools from GitHub. Discover how to take a product from creation to coding to deployment, and how GitHub builds its own software to help teams across the world work and collaborate.
As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub
Thanks!
Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
LinkedIn: http://linkedin.com/company/github
About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com
A
A
Hello
and
welcome
to
day
two
of
satellite
india,
I'm
shonku-
and
I
want
to
thank
you
for
joining
us
today.
We've
got
another
packed
day
of
programming
and
to
start
off,
I
want
to
take
you,
through
a
tour
of
github's
products,
to
show
off
some
of
our
latest
features
and
to
show
you
how
you
can
use
them
together
to
build
software
across
the
world.
A
Now,
yesterday,
erica
was
here
to
celebrate
all
the
amazing
things
that
are
going
on
in
the
github
community
in
india.
Growth
of
the
community
here
has
been
incredible.
In
the
last
year,
1.8
million
developers
have
joined
github
from
india,
and
over
a
million
developers
have
created
their
first
repo
on
github.
A
A
This
community
is
poised
to
double
in
the
next
two
years
and
we're
excited
to
see
what
you
will
build
with
github
next
now
github
is
the
world's
largest
developer
community
and
it
is
for
a
purpose,
and
that
purpose
is
to
build
together.
We
think
of
software
development
as
the
world's
largest
team
sport,
and
we
believe
that
it
is
a
sport
without
borders.
A
Now
I
was
born
in
india
and
I
moved
to
canada
when
I
was
young
to
study
computer
science,
and
I
had
to
move
again
to
the
united
states
to
take
advantage
of
the
best
opportunities
in
tech.
That
was
the
reality
back
then
right.
If
you
wanted
an
opportunity,
you
had
to
move
to
go,
find
it
remote
learning
remote
work,
global
companies.
A
Teams
of
all
shapes
and
sizes
companies
from
all
over
the
world
are
going
remote
and
they're
going
worldwide
to
tap
into
the
best
developers,
whether
they
come
from
mumbai
or
mombasa
or
miami,
and
those
developers
need
to
be
able
to
work
together
on
projects
from
wherever
they
are.
That's
what
I
love
about,
github
github
was
built
for
this
kind
of
collaboration.
A
So
today
I
want
to
take
you
on
a
tour
through
github's
products
and
show
you
how
you
can
use
them
to
build
from
wherever
you
are
now.
Do
you
remember
your
first
time
joining
a
software
team?
I
know
I
do
that
thrill
of
writing
code
and
committing
it
for
the
first
time
and
seeing
it
in
a
product
right,
but
first
there
were
all
those
things
you
had
to
go
through
right.
Setting
up
your
dev
box,
setting
up
your
tools,
getting
your
code
and
looking
through
it
to
learn
going
through
docs
and
style
guides.
A
All
of
those
things
that
you
had
to
learn
before
you
can
contribute
something
without
messing
it
up,
even
with
the
best
mentor
to
help
you
that
could
take
days
and
the
reality
is
today.
You
have
to
do
that.
All
the
time
developers
almost
never
work
on
just
one
thing:
you're,
always
having
to
switch
context,
work
on
different
projects,
fixing
live
site
incidents,
contributing
to
other
teams
code
or
even
just
learning
something
new.
That
is
not
easy.
A
On
average,
it
takes
over
23
minutes
to
switch
context
and
get
into
the
flow,
and
that
is
if
you've
got
everything
set
up
for
you.
Often
it
can
take
a
lot
longer
so
github
we
care
about
this
a
lot
we
want
developers
to
be
able
to
get
into
the
flow
get
into
the
code
and
contribute
whether
they're
joining
a
project
for
the
first
time
or
just
getting
back
into
it
after
a
while
to
show
you
how
github
helps
you
get
in
the
flow.
Here's
neha.
B
Hi,
I'm
neha,
I'm
the
director
of
engineering
here
at
github
for
the
team
that
works
on
discussions,
I'm
pleased
to
announce
that
we've
now
enabled
discussions
on
private
repos,
and
that
means
for
this
private
repo.
We
can
have
our
team
conversations
here
and
leave
our
issues
for
tracking
our
work.
Here
we
have
some
internal
chat
about
skylines.
These
cool
3d
printed
contribution
graphs
that
people
have
created
using
a
website
we
built,
but
we
also
use
discussions
to
talk
about
ideas
in
the
team
and
with
others
in
the
company.
B
My
teammate
diana
had
an
idea
here
the
other
day
about
adding
a
year
selector
to
the
page,
and
I
really
like
that.
So
I
want
us
to
work
on
this.
So
let's
create
an
issue
from
this
discussion
thread
and
track
the
work.
So
I'm
just
going
to
go
in
here
reference
the
issue
give
it
a
title
and
then
I
can
just
scroll
down
and
I
can
create
the
issue.
So
this
shouldn't
be
too
hard
and
I'm
thinking
I
might
be
the
one
to
pick
this
up,
and
so
we
can
do
it
together.
B
Let's
just
take
a
quick
look,
so
I'm
going
to
go
over
I'm
going
to
assign
the
issue
to
myself,
and
you
can
see
that
this
isn't
the
code
base
that
I
work
in
every
day.
This
is
just
for
fun,
so,
rather
than
downloading
all
the
dependencies
to
my
machine
and
getting
a
full
development
environment
set
up
locally,
I
can
open
a
code
space
right
here
in
github
and
I
can
get
my
own
personal
dev
box
in
the
cloud
right
away,
and
this
isn't
just
running
the
visual
code
editor
in
the
cloud.
B
This
is
a
full-blown
personal
development
environment
in
the
cloud.
So,
for
example,
if
I
like
go
over
to
the
terminal-
and
I
type
in
npm-
run
dev
here
in
the
console,
I
can
get
the
full
local
development
experience
as
if
I'd
had
the
code
locally
on
my
machine
codespaces
even
sees
when
my
code
is
running
a
server
on
localhost
and
so
it'll.
Let
me
connect
to
it
across
the
internet,
taking
care
of
all
of
the
https
tunneling
and
authentication
to
ensure
only
I
can
see
what
is
running
on
my
dev
box
in
the
cloud.
B
So
let
me
type
in
my
github
id
nerd
neha
and
let
me
check
out
this
awesome
graph,
so
this
site's
pretty
awesome.
It's
got
like
a
nice
soundtrack
and
the
coolest
part
is
it's
running
on
my
dev
box
in
the
cloud,
but
yeah
2020
isn't
really
a
year.
I
want
to
remember
so.
Let's
get
started
on
that
issue
that
diana
mentioned
by
adding
a
year
selector
here
codespaces
is
already
authenticated
with
github.
So
actually
I
can
actually
just
go
to
the
github
extension
in
vs
code
and
it
has
my
issues
already
listed.
B
B
So
all
I
have
to
do
now
is
take
a
look
at
the
files,
so
I'm
going
to
go
over
I'm
going
to
find
the
form
part
which
I
happen
to
know
is
called
hero.view,
and
I
know
that
the
code
that
I
want
to
add
in
is
between
the
at
symbol
and
the
submit
button.
So
I'm
going
to
quickly
add
the
code
for
a
year
selector
and
then
I'm
going
to
hit
save
now.
This
is
a
full
development
environment.
B
So
if
I
just
jump
back
into
my
application,
we
can
see
it's
refreshing
just
as
if
I
was
running
code
locally
and
it'll
start
to
bring
up
the
selector
there.
It
is
so
I'm
going
to
type
in
my
username
again
and
I'm
going
to
test
it
with
the
2018
year.
I
know
that
I
had
like
a
pretty
good
year
that
year
and
also
I
had
this
like
great
break
for
summer
and
thanksgiving.
B
So
I
want
to
see
if
those
show
up-
and
so
here
we
go
okay,
so
you
can
see
my
skyline
and
you
can
see
that,
like
I
even
at
the
end,
there's
like
some
nice
gaps,
it's
when
I
took
my
end
of
your
vacation
super
seriously,
and
so
this
is
all
running
in
my
private
development
machine
in
the
cloud
I
can
come
in,
I
can
mess
with
the
graph
I
can
scroll
around,
and
so
I
know
that
this
works
and
I'm
ready.
Let's
commit
this
and
let's
share
the
changes
with
the
team.
B
So
what
I
want
to
do
now
is,
I
want
to
go
back
to
my
editor
and
I
want
to
first
commit
that
change
locally.
So
I'm
going
to
go
into
the
get
view
and
you
can
notice.
It
already
includes
a
link
to
the
issue
that
we're
working
on
and
so
then
I
can
go
ahead.
I
can
commit
it
and
now
I'm
going
to
create
a
pull
request,
so
I
can
do
that
by
going
straight
to
the
extension
and
then
I'm
going
to
go
into
my
github
view,
I'm
going
to
create
a
new
pull
request.
B
It's
going
to
figure
out
which
branch
I
want
to
compare
to,
and
it's
going
to
even
publish
the
branch
for
me.
So
I'm
just
going
to
scroll
down
here
hit
create
and
then
I
can
create
the
pull
request
and
it's
going
to
do
all
the
work
of
publishing
the
branch,
pushing
the
changes
in
the
server
and
even
creating
the
pull
request
in
the
server.
So
you
can
see
my
pr
it's
like
right
here.
So
if
I
go
back
into
my
repo
on
github,
I
can
navigate
over
to
the
pull
request
tab.
So
let's
do
that?
B
Really
quickly
and
there
you
can
see
my
pr
is
available
your
selector
for
graph,
and
you
can
see
that
it's
ready
for
my
team
to
review
and
I
can
see
that
the
ci
builds
have
already
kicked
off.
So
I
can
to
verify
my
change.
So
let
me
go
in
I'm
going
to
tag
this
with
the
enhancement
label
and
then
I'm
gonna
you
make
use
of
this
super
cool
new
feature.
B
It's
called
auto,
merge
and
github,
and
so
what
I'm
doing
here
is
I'm
having
the
pr
get
merged
automatically
as
soon
as
all
the
checks
are
complete
and
the
code
has
been
reviewed
by
the
team,
and
so
I
don't
have
to
do
anything
here,
and
this
leaves
me
free
to
get
on
with
my
next
change.
In
the
meantime,
let
me
hand
you
back
to
shanku.
A
Thanks
neja
now,
once
you've
written
your
code,
it's
time
to
get
it
reviewed
and
committed
now.
Code
reviews
have
also
changed
in
this
new
world
used
to
be
that
you
could
invite
someone
over
to
look
over
your
shoulder
and
review
your
changes
and
give
you
a
quick
thumbs
up,
but
now
that
you're
working
on
a
distributed
or
remote
team,
you
still
need
that
review.
A
Better
prs
also
means
not
just
having
human
helpers,
but
the
bots
github
actions
and
our
amazing
ecosystem
provides
an
integrated
ci
platform
with
thousands
of
custom
actions
written
by
our
community
that
can
automate
all
sorts
of
reviews
running
your
unit
tests,
applying
linters
and
style
guides.
Checking
your
dependencies
and
just
helping
you
commit
better
code
to
show
us
more
here
is
a
tool.
C
I'm
atul
and
I
work
on
the
databases
team
here
in
hyderabad.
This
is
the
pr
from
neha
where
she
has
added
a
new
ear
selector
to
the
site
that
we
are
building
for
every
change
we
make
to
the
site
we
build
and
test
it
automatically
using
data
actions.
Let
me
show
you
the
ci
bill
for
neha's
latest
changes.
If
I
go
into
the
assembly
view,
you
can
see
the
brand
new
visualizer
showing
us
running
the
build
and
test
steps
on
both
mac
and
linux
machines
all
at
the
same
time.
C
This
takes
advantage
of
data
actions
and
our
hosted
build
runners
which
provide
you
with
secure,
build
servers
on
demand.
All
of
this
infrastructure
is
managed
for
you
by
our
team
at
github
so
that
you
can
add
new
build
machines
whenever
you
need
them
for
either
linux
windows
or
the
mac.
Let's
go
back.
Let's
look
at
how
the
build
is
configured.
Our
workflows
are
defined
in
the
dark
data
folder
under
workflows.
We
are
going
to
look
at
the
ci
build.
C
First,
we
can
see
that
it
is
triggered
by
new
changes
in
the
main
branch,
but
also
by
any
pull
requests
that
are
targeting
the
main
branch
we
also
define
which
operating
system
and
node
versions.
We
want
to
run
our
build
on,
and
then
we
build
our
code
on
the
linter
and
do
a
full
test
shoot
pass.
The
actions
community
is
fantastic
with
over
7000
open
source
actions
in
the
marketplace
in
the
ci
build.
We
have
added
an
awesome
community
action
from
tim,
lucas
and
joseph
peterson
that
will
update
draft
release.
C
Note
for
you,
based
on
your
issues
and
full
requests.
So
that's
that's
the
power
of
community
for
you
that
you
can
use
to
transfer
ci.
We
also
create
and
deploy
a
test
environment
in
the
cloud
for
every
single
pull
request.
This
makes
it
easy
for
us
to
review
the
changes
in
a
working
environment.
So
let's
take
a
look
at
the
dev
test
development
workflow,
which
is
run
in
parallel
alongside
our
ci
bit.
So,
as
you
saw,
this
is
triggered
by
pushes
domain
along
with
new
pull
request.
C
We
come
in
get
the
code
and
then
deploy
it
to
our
cloud
provider
using
a
secret
which
we
store
securely
inside
github's
built-in
secret
store,
we've
also
added
a
job
to
this
workflow
that
will
come
back
and
destroy
the
environment
when
the
pull
request
is
closed,
to
keep
our
costs
down.
So
let's
go
back
to
the
pr
from
the
pr
from
neha
and
review
it.
C
C
C
C
The
code,
the
code
looks
good,
so,
let's
just
say,
lgtm
and
quickly
approve
the
code.
Now
because
it
has
enabled
auto
merge.
S1
has
approved
the
change,
the
code
is
deployed,
the
code
is
merged
automatically,
and
data
actions
take
care
of
destroying
the
test
environment
for
me,
so
everything
just
works.
End-To-End
back
to
shangri.
A
A
One
leaked
secret,
one
vulnerable
piece
of
code,
one
insecure
dependency
can
cost
you
time,
cost
you
money
and
cost
your
customers
trust
now
we're
humans
and
humans
make
mistakes.
It
turns
out.
The
majority
of
security
vulnerabilities
are
just
human
mistakes
and
once
those
mistakes
get
into
code,
they're
hard
to
get
out.
D
In
our
example.
Here
we
have
advanced
security
enabled
in
our
organization,
and
this
allows
us
to
easily
switch
on
code
scanning
and
secret
scanning
for
our
private
repos,
but
everyone
can
still
use
these
features
on
your
public
repos
for
free
just
go
to
the
security
section
of
your
repo
settings
and
switch
it
on
there.
D
I
can
get
an
overview
of
the
security
situation
for
my
project
from
the
security
tab
in
the
repo
beginning
with
supply
chain
issues.
Here
we
have
dependebot
enabled
it
is
automatically
looking
for
vulnerabilities
with
my
dependencies
and
it
will
create
a
pull
request
for
me
if
one
of
them
needs
updating.
D
D
D
So
that's
known,
vulnerabilities
and
sequence
taken
care
of,
but
what
about
our
unknown
vulnerabilities
with
codeql
from
github
we're
able
to
scan
our
code
base
looking
for
code
which
could
be
introducing
potential
security
vulnerabilities
into
the
code
that
we're
writing?
As
you
can
see,
it's
identified
one
here
for
me.
I
can
show
the
code
part
that
was
found
with
code,
ql's
analysis
tools,
and
I
can
see
that
this
is
definitely
an
issue.
D
However,
it
doesn't
look
like
it'll
lead
to
a
major
exploit
in
our
case,
but
let's
create
a
quick
issue
from
the
code,
so
we
don't
forget
about
it.
This
should
be
a
simple
fix
to
explicitly
to
string
the
value
from
the
url
I'll.
Also
mark
this
as
a
good
first
issue
in
case
someone
wants
to
pick
this
one
up
once
I'm
happy
we'll
save
the
issue
to
make
sure
we
don't
lose
track
of
the
work.
D
A
Thank
you
niroshan.
Now,
we've
got
our
code
written
reviewed
and
committed
where
our
code
really
belongs,
is
in
our
users
hands,
and
that
means
shipping
doing
the
functional
testing
sharing
with
stakeholders
and
getting
them
to
sign
off
and
releasing
the
production
and
celebrating
together.
Now,
github's
new
tools
were
designed
to
make
it
easy
to
test
and
release
together
as
a
team
to
show
us
more.
Here's
katie.
E
E
E
E
Then
it
will
run
some
end
to
end
smoke
tests
before
finally
deploying
to
production.
While
all
of
that
is
running,
let
me
show
you
how
I've
set
this
up.
Let's
take
a
look
at
the
code
in
another
tab
in
the
github
workflows,
folder
we'll
find
the
releases.yaml
file
in
the
release.
Yml,
you
can
see
I've
set
up
a
couple
of
different
triggers
a
manual
trigger
with
workflow
dispatch
as
well
as
triggers
based
on
when
a
release
is
published
in
the
deploy
staging
job.
I
specify
the
environment
name
and
url,
where
this
will
be
available.
E
E
Now
these
steps
are
identical,
yet
they
publish
to
different
places.
That's
because
we
define
a
different
publish
token
for
each
environment.
Let
me
show
you
how
we
do
this.
I
head
into
project
settings
then,
in
the
new
environment
section
I
have
staging
and
production
on
the
staging
environment.
You
can
see
we
have
a
published
token
defined
in
github's
encrypted
secret
vault,
even
as
admin.
I
only
have
access
to
update
this.
I
can't
view
it
in
the
ui
going
back
to
production.
E
I
have
the
production
publish
token
defined
in
our
secrets
here
as
well,
but
what's
more
interesting
is
that
you
can
see
I've
set
this
up
to
require
manual
approval
before
code
is
deployed
to
production.
Only
people
from
this
team
can
permit
code
to
go,
live
and
there's
a
full
audit
trail
to
see
who
approved
it.
E
E
A
A
Get
code
reviewed
with
your
peers
with
the
help
of
automated
ci,
to
keep
your
code
and
your
secrets
and
your
dependencies
secure
and
test
and
ship
and
celebrate
together
now
all
asynchronous
all
remote
friendly
all
available
from
anywhere
in
the
world
on
github's
planet
scale
cloud.
Now
software
teams
all
across
the
world
are
using
github
to
do
incredible
things.
One
such
story
comes
from
india's
own
infosys.
F
Like
our
most
visionary
clients
partners,
our
goal
is
to
become
a
completely
knowledge
and
data
driven
organization
with
agility
built
into
our
core,
so
that
we
can
sense
all
the
business
changes
happening
around
us
and
continuously
evolve
in
response
at
infosys.
We
are
envisioning
ourselves
to
be
a
live
enterprise
powered
by
our
digital
platforms.
F
For
instance,
infosys
devsecops
platform,
polycloud
meridian
leap,
modernization
suit
are
some
of
the
examples
of
assets
that
power
this
for
us.
Github
is
a
critical
element
of
this
ecosystem
and
is
central
to
driving
developer
productivity,
secure
sdlc,
inner
sourcing,
reusability
and
augmenting
the
developer.
Analytics
for
us,
it
is
unifying
the
experience
of
of
our
developers
by
a
variety
of
integrations
around
the
robust
devsecops
ecosystem.
F
It
is
also
a
key
enabler
for
a
live
enterprise
store
and
marketplace
where
we
plan
to
bring
together
the
community
of
cloud
builders
on
cobalt
from
amongst
our
partners,
clients,
open
source,
academia
and
the
startups
to
drive
contributions
and
consumption
of
various
assets,
as
well
as
enhance
the
ecosystem
with
an
open
source.
First
thinking
something,
I
believe
that
any
forward-looking
enterprise,
engineering
teams
and
developers
would
appreciate
in
a
big
big
way,
as
the
github
team
continues
to
drive
the
roadmap.
F
A
Is
exciting
to
see
what
companies
like
infosys
and
you,
the
developer
community
here
in
india,
how
you're
using
github
every
day
to
create
amazing
things?
Thank
you.
You
inspire
us
to
keep
making
github
better
in
just
the
last
six
months.
We
have
shipped
over
100
new
features
and
improvements,
including
many
of
the
features
you
just
saw.
All
you
need
to
do
to
get
started
with.
Github
is
available
for
free
on
github.com
for
developers
and
teams
of
any
size.
A
So
if
you're
just
learning
to
code
or
contributing
to
open
source
or
starting
a
new
team
or
or
starting
your
own
startup,
you
can
do
that
on
github
for
free
today,
all
right,
thank
you
for
joining
us
on
this
tour
today
this
was
fun
to
do.
I
hope
you
enjoy
using
github
as
much
as
we
love
building
it.
We're
not
just
building
developer
tools
for
global
teams.
We
are
one
ourselves.
A
Github
has
always
been
a
remote
first
company
and
we
now
have
developers
from
over
15
countries
working
together
as
one
team
and
a
big
part
of
our
team
is
the
github
team
in
india,
they're
building
github
on
github
with
the
rest
of
us.
So
in
closing
it's
my
pleasure
to
introduce
you
to
the
github
team
here
in
india.