How to submit your first pull request on GitHub in 100 seconds. Fork the repo below, then contribute a PR to receive a free hologram sticker in the mail https://github.com/fireship-io/git-sticker

How to Participate on Github https://fireship.io/snippets/git-how-to-participate-on-github/
GitHub PR Docs Official https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests

#git #freestuff #100SecondsOfCode

Install the quiz app 🤓

iOS https://itunes.apple.com/us/app/fireship/id1462592372?mt=8
Android https://play.google.com/store/apps/details?id=io.fireship.quizapp

Upgrade to Fireship PRO at https://fireship.io/pro
Use code lORhwXd2 for 25% off your first payment. 

My VS Code Theme

- Atom One Dark 
- vscode-icons
- Fira Code Font
2024-02-04T06:19:14.488Z
nova-2
2-general-nova
2024-01-09.29447
30089e05-99d1-4376-b32e-c263170674af
e20f97be-fede-475f-9e4c-02e8e2ff2004
ef6d0db0a6812e18415789b7f8da4fca5889d4351b6efd08518501c9bb394f48
67875a7f-c9c4-48a0-aa55-5bdb8a91c34a
deprecated
Pull request, a way for you to submit a contribution to another developer's repository on GitHub.
1st, find a GitHub repo that you want to contribute to.
This looks like a good one.
Submit a pull request and get a free sticker in the mail.
The first thing you'll need to do is fork the repo.
When you fork a repo, it will be copied over to your own GitHub account.
The fork maintains a link to the original upstream repo.
And that means you can pull in future changes when necessary.
From there, you'll want to clone your fork onto your local system so you can start developing your own changes.
Next, open up the project in your preferred code editor.
Use the git branch command to create a new branch that describes the changes that you're going to make.
Use git switch or checkout to move into that branch.
Now it's your job to make the software better.
This particular repo tells us how to encrypt our address so we can upload it and get a free sticker.
After you make your changes, use git add to stage the files and then git commit to commit them to the repo.
Now, we need to get our files back to GitHub.
Git push is the command that can do that.
We tell it to use origin, which is our remote repository on GitHub, followed by the branch name that we're currently working on.
When we go back to our fork on GitHub, we We should see our changes as well as a button to open a new pull request.
Make sure that you follow the contribution guidelines for the owner's repo carefully because it's typically bad GitHub etiquette to Submit a pull request without first discussing it in the issues.
But if you're confident about your changes, go ahead and click the green button.
And that's all there is to it.
After your PR is merged, You should receive a sticker in the mail a few weeks later.
But we still have a few seconds to kill, so here's a little pro tip.
When working with a fork locally, you can keep it in sync with the original by first adding a remote link to the upstream repo.
Now when things change in that repo, you can use git fetch to download the changes and then git rebase to add those changes on top of your existing work.
And stay tuned for a future video all about Git rebase.
This has been your first GitHub pull request in 100 seconds.
Make sure to hit the like button if you wanna see more short videos like this.
Thanks for watching and I will see you in the next one.

Speaker 0: Pull request, a way for you to submit a contribution to another developer's repository on GitHub. 1st, find a GitHub repo that you want to contribute to. This looks like a good one. Submit a pull request and get a free sticker in the mail. The first thing you'll need to do is fork the repo.

When you fork a repo, it will be copied over to your own GitHub account. The fork maintains a link to the original upstream repo. And that means you can pull in future changes when necessary. From there, you'll want to clone your fork onto your local system so you can start developing your own changes. Next, open up the project in your preferred code editor.

Use the git branch command to create a new branch that describes the changes that you're going to make. Use git switch or checkout to move into that branch. Now it's your job to make the software better. This particular repo tells us how to encrypt our address so we can upload it and get a free sticker. After you make your changes, use git add to stage the files and then git commit to commit them to the repo.

Now, we need to get our files back to GitHub. Git push is the command that can do that. We tell it to use origin, which is our remote repository on GitHub, followed by the branch name that we're currently working on. When we go back to our fork on GitHub, we We should see our changes as well as a button to open a new pull request. Make sure that you follow the contribution guidelines for the owner's repo carefully because it's typically bad GitHub etiquette to Submit a pull request without first discussing it in the issues.

But if you're confident about your changes, go ahead and click the green button. And that's all there is to it. After your PR is merged, You should receive a sticker in the mail a few weeks later. But we still have a few seconds to kill, so here's a little pro tip. When working with a fork locally, you can keep it in sync with the original by first adding a remote link to the upstream repo.

Now when things change in that repo, you can use git fetch to download the changes and then git rebase to add those changes on top of your existing work. And stay tuned for a future video all about Git rebase. This has been your first GitHub pull request in 100 seconds. Make sure to hit the like button if you wanna see more short videos like this. Thanks for watching and I will see you in the next one.
Pull request, a way for you to submit a contribution to another developer's repository on GitHub. 1st, find a GitHub repo that you want to contribute to. This looks like a good one. Submit a pull request and get a free sticker in the mail. The first thing you'll need to do is fork the repo. When you fork a repo, it will be copied over to your own GitHub account. The fork maintains a link to the original upstream repo.
And that means you can pull in future changes when necessary. From there, you'll want to clone your fork onto your local system so you can start developing your own changes. Next, open up the project in your preferred code editor. Use the git branch command to create a new branch that describes the changes that you're going to make. Use git switch or checkout to move into that branch. Now it's your job to make the software better. This particular repo tells us how to encrypt our address so we can upload it and get a free sticker.
software
software development
After you make your changes, use git add to stage the files and then git commit to commit them to the repo. Now, we need to get our files back to GitHub. Git push is the command that can do that. We tell it to use origin, which is our remote repository on GitHub, followed by the branch name that we're currently working on. When we go back to our fork on GitHub, we We should see our changes as well as a button to open a new pull request. Make sure that you follow the contribution guidelines for the owner's repo carefully because it's typically bad GitHub etiquette to Submit a pull request without first discussing it in the issues. But if you're confident about your changes, go ahead and click the green button. And that's all there is to it. After your PR is merged, You should receive a sticker in the mail a few weeks later. But we still have a few seconds to kill, so here's a little pro tip. When working with a fork locally, you can keep it in sync with the original by first adding a remote link to the upstream repo. Now when things change in that repo, you can use git fetch to download the changes and then git rebase to add those changes on top of your existing work. And stay tuned for a future video all about Git rebase. This has been your first GitHub pull request in 100 seconds. Make sure to hit the like button if you wanna see more short videos like this. Thanks for watching and I will see you in the next one.
Pull request, a way for you to submit a contribution to another developer's repository on GitHub. 1st, find a GitHub repo that you want to contribute to. This looks like a good one. Submit a pull request and get a free sticker in the mail. The first thing you'll need to do is fork the repo. When you fork a repo, it will be copied over to your own GitHub account. The fork maintains a link to the original upstream repo. And that means you can pull in future changes when necessary. From there, you'll want to clone your fork onto your local system so you can start developing your own changes. Next, open up the project in your preferred code editor. Use the git branch command to create a new branch that describes the changes that you're going to make. Use git switch or checkout to move into that branch. Now it's your job to make the software better. This particular repo tells us how to encrypt our address so we can upload it and get a free sticker. After you make your changes, use git add to stage the files and then git commit to commit them to the repo. Now, we need to get our files back to GitHub. Git push is the command that can do that. We tell it to use origin, which is our remote repository on GitHub, followed by the branch name that we're currently working on. When we go back to our fork on GitHub, we We should see our changes as well as a button to open a new pull request. Make sure that you follow the contribution guidelines for the owner's repo carefully because it's typically bad GitHub etiquette to Submit a pull request without first discussing it in the issues. But if you're confident about your changes, go ahead and click the green button. And that's all there is to it. After your PR is merged, You should receive a sticker in the mail a few weeks later. But we still have a few seconds to kill, so here's a little pro tip. When working with a fork locally, you can keep it in sync with the original by first adding a remote link to the upstream repo. Now when things change in that repo, you can use git fetch to download the changes and then git rebase to add those changes on top of your existing work. And stay tuned for a future video all about Git rebase. This has been your first GitHub pull request in 100 seconds. Make sure to hit the like button if you wanna see more short videos like this. Thanks for watching and I will see you in the next one.
Pull
pull
request,
request
a
a
way
way
for
for
you
you
to
to
submit
submit
a
a
contribution
contribution
to
to
another
another
developer's
developer's
repository
repository
on
on
GitHub.
github
1st,
1st
find
find
a
a
GitHub
github
repo
repo
that
that
you
you
want
want
to
to
contribute
contribute
to.
to
This
this
looks
looks
like
like
a
a
good
good
one.
one
Submit
submit
a
a
pull
pull
request
request
and
and
get
get
a
a
free
free
sticker
sticker
in
in
the
the
mail.
mail
The
the
first
first
thing
thing
you'll
you'll
need
need
to
to
do
do
is
is
fork
fork
the
the
repo.
repo
When
when
you
you
fork
fork
a
a
repo,
repo
it
it
will
will
be
be
copied
copied
over
over
to
to
your
your
own
own
GitHub
github
account.
account
The
the
fork
fork
maintains
maintains
a
a
link
link
to
to
the
the
original
original
upstream
upstream
repo.
repo
And
and
that
that
means
means
you
you
can
can
pull
pull
in
in
future
future
changes
changes
when
when
necessary.
necessary
From
from
there,
there
you'll
you'll
want
want
to
to
clone
clone
your
your
fork
fork
onto
onto
your
your
local
local
system
system
so
so
you
you
can
can
start
start
developing
developing
your
your
own
own
changes.
changes
Next,
next
open
open
up
up
the
the
project
project
in
in
your
your
preferred
preferred
code
code
editor.
editor
Use
use
the
the
git
git
branch
branch
command
command
to
to
create
create
a
a
new
new
branch
branch
that
that
describes
describes
the
the
changes
changes
that
that
you're
you're
going
going
to
to
make.
make
Use
use
git
git
switch
switch
or
or
checkout
checkout
to
to
move
move
into
into
that
that
branch.
branch
Now
now
it's
it's
your
your
job
job
to
to
make
make
the
the
software
software
better.
better
This
this
particular
particular
repo
repo
tells
tells
us
us
how
how
to
to
encrypt
encrypt
our
our
address
address
so
so
we
we
can
can
upload
upload
it
it
and
and
get
get
a
a
free
free
sticker.
sticker
After
after
you
you
make
make
your
your
changes,
changes
use
use
git
git
add
add
to
to
stage
stage
the
the
files
files
and
and
then
then
git
git
commit
commit
to
to
commit
commit
them
them
to
to
the
the
repo.
repo
Now,
now
we
we
need
need
to
to
get
get
our
our
files
files
back
back
to
to
GitHub.
github
Git
git
push
push
is
is
the
the
command
command
that
that
can
can
do
do
that.
that
We
we
tell
tell
it
it
to
to
use
use
origin,
origin
which
which
is
is
our
our
remote
remote
repository
repository
on
on
GitHub,
github
followed
followed
by
by
the
the
branch
branch
name
name
that
that
we're
we're
currently
currently
working
working
on.
on
When
when
we
we
go
go
back
back
to
to
our
our
fork
fork
on
on
GitHub,
github
we
we
We
we
should
should
see
see
our
our
changes
changes
as
as
well
well
as
as
a
a
button
button
to
to
open
open
a
a
new
new
pull
pull
request.
request
Make
make
sure
sure
that
that
you
you
follow
follow
the
the
contribution
contribution
guidelines
guidelines
for
for
the
the
owner's
owner's
repo
repo
carefully
carefully
because
because
it's
it's
typically
typically
bad
bad
GitHub
github
etiquette
etiquette
to
to
Submit
submit
a
a
pull
pull
request
request
without
without
first
first
discussing
discussing
it
it
in
in
the
the
issues.
issues
But
but
if
if
you're
you're
confident
confident
about
about
your
your
changes,
changes
go
go
ahead
ahead
and
and
click
click
the
the
green
green
button.
button
And
and
that's
that's
all
all
there
there
is
is
to
to
it.
it
After
after
your
your
PR
pr
is
is
merged,
merged
You
you
should
should
receive
receive
a
a
sticker
sticker
in
in
the
the
mail
mail
a
a
few
few
weeks
weeks
later.
later
But
but
we
we
still
still
have
have
a
a
few
few
seconds
seconds
to
to
kill,
kill
so
so
here's
here's
a
a
little
little
pro
pro
tip.
tip
When
when
working
working
with
with
a
a
fork
fork
locally,
locally
you
you
can
can
keep
keep
it
it
in
in
sync
sync
with
with
the
the
original
original
by
by
first
first
adding
adding
a
a
remote
remote
link
link
to
to
the
the
upstream
upstream
repo.
repo
Now
now
when
when
things
things
change
change
in
in
that
that
repo,
repo
you
you
can
can
use
use
git
git
fetch
fetch
to
to
download
download
the
the
changes
changes
and
and
then
then
git
git
rebase
rebase
to
to
add
add
those
those
changes
changes
on
on
top
top
of
of
your
your
existing
existing
work.
work
And
and
stay
stay
tuned
tuned
for
for
a
a
future
future
video
video
all
all
about
about
Git
git
rebase.
rebase
This
this
has
has
been
been
your
your
first
first
GitHub
github
pull
pull
request
request
in
in
100
100
seconds.
seconds
Make
make
sure
sure
to
to
hit
hit
the
the
like
like
button
button
if
if
you
you
wanna
wanna
see
see
more
more
short
short
videos
videos
like
like
this.
this
Thanks
thanks
for
for
watching
watching
and
and
I
i
will
will
see
see
you
you
in
in
the
the
next
next
one.
one
success
The speaker explains how to submit a contribution request to another developer's repository on GitHub. They provide instructions on how to fork a repo, create a new one, and upload changes to GitHub. The speaker also gives a pro tip on how to work with a fork locally and mentions a future video about Git rebase.
GitHub Pull Request in 100 Seconds - Git a FREE sticker 🔥
Pull request, a way for you to submit a contribution to another developer's repository on GitHub. 1st, find a GitHub repo that you want to contribute to. This looks like a good one. Submit a pull request and get a free sticker in the mail. The first thing you'll need to do is fork the repo. When you fork a repo, it will be copied over to your own GitHub account. The fork maintains a link to the original upstream repo. And that means you can pull in future changes when necessary. From there, you'll want to clone your fork onto your local system so you can start developing your own changes. Next, open up the project in your preferred code editor. Use the git branch command to create a new branch that describes the changes that you're going to make. Use git switch or checkout to move into that branch. Now it's your job to make the software better. This particular repo tells us how to encrypt our address so we can upload it and get a free sticker. After you make your changes, use git add to stage the files and then git commit to commit them to the repo. Now, we need to get our files back to GitHub. Git push is the command that can do that. We tell it to use origin, which is our remote repository on GitHub, followed by the branch name that we're currently working on. When we go back to our fork on GitHub, we We should see our changes as well as a button to open a new pull request. Make sure that you follow the contribution guidelines for the owner's repo carefully because it's typically bad GitHub etiquette to Submit a pull request without first discussing it in the issues. But if you're confident about your changes, go ahead and click the green button. And that's all there is to it. After your PR is merged, You should receive a sticker in the mail a few weeks later. But we still have a few seconds to kill, so here's a little pro tip. When working with a fork locally, you can keep it in sync with the original by first adding a remote link to the upstream repo. Now when things change in that repo, you can use git fetch to download the changes and then git rebase to add those changes on top of your existing work. And stay tuned for a future video all about Git rebase. This has been your first GitHub pull request in 100 seconds. Make sure to hit the like button if you wanna see more short videos like this. Thanks for watching and I will see you in the next one.
The speaker explains how to submit a contribution request to another developer's repository on GitHub. They provide instructions on how to fork a repo, create a new one, and upload changes to GitHub. The speaker also gives a pro tip on how to work with a fork locally and mentions a future video about Git rebase.