-
Not Synced
Git is an excellent,
and industry-recognized
-
Not Synced
version-control system.
-
Not Synced
GitHub.com, the website,
makes that accessible to everyone.
-
Not Synced
♪ (whimsical theme music) ♪
-
Not Synced
It's easy to think that you could host
-
Not Synced
your Git repositories anywhere.
-
Not Synced
There's plenty of services,
-
Not Synced
and plenty of tools for you to host them
-
Not Synced
even within your own corporate firewall.
-
Not Synced
But there's more
than just hosting your code.
-
Not Synced
We're talking about changing software,
-
Not Synced
and that includes all types,
and all facets of collaboration:
-
Not Synced
filing issues, organizing repositories
so they're easy to find,
-
Not Synced
being able to mention
the contributors by user name,
-
Not Synced
and the ability to have control
over the inbound changes,
-
Not Synced
through the concept
that we call pull requests.
-
Not Synced
All of these are facilitated
by GitHub.com,
-
Not Synced
a collaboration platform
that also hosts Git repositories.
-
Not Synced
♪ (whimsical theme music) ♪
-
Not Synced
Your first interaction with GitHub
is likely through the Explore page,
-
Not Synced
finding a bit of open source
-
Not Synced
that solves a need
in your current application.
-
Not Synced
But soon, you'll find
you want to file an issue,
-
Not Synced
or perhaps even
submit a change to a project
-
Not Synced
that improves it, or corrects a defect.
-
Not Synced
Those are all things
that are made possible
-
Not Synced
by the GitHub platform.
-
Not Synced
You'll find that we have solutions,
-
Not Synced
such as an integrated defect tracker,
-
Not Synced
and the process of pull requests,
-
Not Synced
to which code change can get reviewed,
-
Not Synced
commented on, refined,
and then finally accepted,
-
Not Synced
even for people
that are not core contributors
-
Not Synced
to the project itself.
-
Not Synced
GitHub adds further innovations
that allow Git to go places
-
Not Synced
that it wouldn't ordinarily
have been welcome.
-
Not Synced
For example, we have an SvnBridge
that allows any Git repository
-
Not Synced
to be treated as a subversion repository.
-
Not Synced
This often facilitates a slow migration
-
Not Synced
of continuous integration infrastructure,
-
Not Synced
build scripts, or other automation
-
Not Synced
that you've built into
your release process.