Go to file
Brendan Forster a229d899a9
Merge pull request #6630 from desktop/clean-up-no-changes-blankslate-feature-flag
Clean up no changes blankslate feature flag
2019-01-18 08:37:48 -04:00
.circleci add circleci step 2018-09-12 16:26:36 -07:00
.github Apply suggestions from code review 2018-12-28 13:39:51 -04:00
.vscode rename jest.config.js to jest.unit.config.js to differentiate from integration tests 2019-01-16 13:18:15 -04:00
app Merge branch 'development' into clean-up-no-changes-blankslate-feature-flag 2019-01-17 15:37:25 -04:00
docs Add screenshots 2019-01-14 13:08:20 -05:00
eslint-rules Enforce 'use strict' (non-)use 2018-01-06 06:34:12 -05:00
gemoji@50865e8895 Get some gemoji 2016-09-02 16:44:44 -04:00
script Merge pull request #6640 from desktop/use-promises-theyre-pretty-neat 2019-01-17 09:11:44 -08:00
tslint-rules Revert "Revert "ESLint for great justice: Episode I"" 2017-10-19 19:01:08 -04:00
vendor Merge branch 'master' into axe-feature-flags-or-body-spray-you-decide 2018-11-26 10:17:59 -07:00
.babelrc Teach babel to understand dynamic import statements 2018-05-22 15:43:50 +02:00
.codecov.yml Merge pull request #6150 from desktop/codecov-granularity 2018-11-20 13:06:51 -04:00
.eslintignore Update .eslintignore 2019-01-07 08:55:10 -04:00
.eslintrc.yml pull eslint into yarn scripts 2018-11-19 12:11:53 -08:00
.gitattributes Don't normalize line endings in fixture repositories on Windows 2018-01-28 08:06:52 +01:00
.gitignore ignore any xml file generated to be read by junit 2018-12-28 16:12:16 -04:00
.gitmodules switched this submodule over to using HTTPS 2017-04-11 17:52:04 +10:00
.node-version newlineeee 2018-11-12 16:07:48 -04:00
.nvmrc upgrade tooling version of Node to last 8.x release 2018-11-09 16:44:26 -04:00
.prettierignore update prettier and format SCSS files 2018-02-02 10:47:01 +11:00
.prettierrc.yml Upgrade Prettier to 1.14 (beta) 2018-07-18 06:42:46 -04:00
.python-version add python-version 2018-09-03 17:53:12 -07:00
.tool-versions upgrade tooling version of Node to last 8.x release 2018-11-09 16:44:26 -04:00
.travis.yml remove master from travis.yml 2018-12-27 15:05:21 -08:00
.yarnrc upgrade yarn to 1.12.3 2018-11-21 14:47:37 -04:00
appveyor.yml remove master in appveyor.yml 2018-12-27 15:05:21 -08:00
azure-pipelines.yml only upload the unit test coverage results for now 2019-01-03 13:08:19 -04:00
changelog.json When in doubt, ask Billy 2019-01-17 15:31:19 +01:00
CODE_OF_CONDUCT.md Update contact behavior to be more clear 2018-08-16 08:01:05 -07:00
LICENSE Remove the date range 2017-04-10 13:43:44 -04:00
package.json Merge pull request #6440 from desktop/use-fs-admin-for-installing-shortcut 2019-01-17 12:14:21 -06:00
README.md remove references to master in docs 2018-12-27 15:38:17 -08:00
tsconfig.json fix tslint for vscode 2018-11-14 16:54:27 -08:00
tslint.json move deprecation rule to root 2018-09-13 09:03:50 -07:00
yarn.lock Merge pull request #6440 from desktop/use-fs-admin-for-installing-shortcut 2019-01-17 12:14:21 -06:00

GitHub Desktop

Travis CircleCI AppVeyor Build Status Azure DevOps Pipelines Build Status license 90+% TypeScript

GitHub Desktop is an open source Electron-based GitHub app. It is written in TypeScript and uses React.

GitHub Desktop screenshot - Windows

Where can I get it?

Download the official installer for your operating system:

There are several community-supported package managers that can be used to install Github Desktop.

  • Windows users can install using Chocolatey package manager: c:\> choco install github-desktop
  • macOS users can install using Homebrew package manager: $ brew cask install github
  • Arch Linux users can install the latest version from the AUR.

You can install this alongside your existing GitHub Desktop for Mac or GitHub Desktop for Windows application.

NOTE: there is no current migration path to import your existing repositories into the new application - you can drag-and-drop your repositories from disk onto the application to get started.

Beta Channel

Want to test out new features and get fixes before everyone else? Install the beta channel to get access to early builds of Desktop:

Is GitHub Desktop right for me? What are the primary areas of focus?

This document describes the focus of GitHub Desktop and who the product is most useful for.

And to see what the team is working on currently and in the near future, check out the GitHub Desktop roadmap.

I have a problem with GitHub Desktop

Note: The GitHub Desktop Code of Conduct applies in all interactions relating to the GitHub Desktop project.

First, please search the open issues and closed issues to see if your issue hasn't already been reported (it may also be fixed).

There is also a list of known issues that are being tracked against Desktop, and some of these issues have workarounds.

If you can't find an issue that matches what you're seeing, open a new issue, choose the right template and provide us with enough information to investigate further.

The issue I reported isn't fixed yet. What can I do?

If nobody has responded to your issue in a few days, you're welcome to respond to it with a friendly ping in the issue. Please do not respond more than a second time if nobody has responded. The GitHub Desktop maintainers are constrained in time and resources, and diagnosing individual configurations can be difficult and time consuming. While we'll try to at least get you pointed in the right direction, we can't guarantee we'll be able to dig too deeply into any one person's issue.

How can I contribute to GitHub Desktop?

The CONTRIBUTING.md document will help you get setup and familiar with the source. The documentation folder also contains more resources relevant to the project.

If you're looking for something to work on, check out the help wanted label.

More Resources

See desktop.github.com for more product-oriented information about GitHub Desktop.

License

MIT

The MIT license grant is not for GitHub's trademarks, which include the logo designs. GitHub reserves all trademark and copyright rights in and to all GitHub trademarks. GitHub's logos include, for instance, the stylized Invertocat designs that include "logo" in the file title in the following folder: logos.

GitHub® and its stylized versions and the Invertocat mark are GitHub's Trademarks or registered Trademarks. When using GitHub's logos, be sure to follow the GitHub logo guidelines.