GitHub Desktop Focus on what matters instead of fighting with Git. Whether you're new to Git or a seasoned user, GitHub Desktop simplifies your development workflow. Download for macOS Download for Windows (64bit) Download for macOS or Windows (msi) Download for Windows. By downloading, you agree to the Open Source Applications Terms. Our software library provides a free download of GitHub Desktop 224.0 for Mac. This free Mac application is an intellectual property of GitHub, Inc. The size of the latest installation package available for download is 28.2 MB. Our antivirus analysis shows that this Mac download is safe. The program belongs to Developer Tools. App Cleaner & Uninstaller is a special tool used to completely uninstall programs on a Mac in just a few clicks. Watch the video to see how it is easy to uninstall GitHub with App Cleaner & Uninstaller or follow step-by-step guide.
When your app is public, anyone can install your app on their repository through the GitHub Marketplace or an installation URL. When your app is private, you can only install the app on repositories that you own.
Note: Your GitHub App will have access to any repositories the app creates, even if someone only installs your app on selected repositories.
Installing your private GitHub App on your repository
Once you create a private GitHub App, you can install it on one of your org or user repositories. For more information, see 'Private installation flow.'
Offering your app in the GitHub Marketplace
You can offer a paid or free version of your app in GitHub Marketplace, where people can search for and view details about your app. GitHub Marketplace automatically installs a GitHub App when an order is complete.
See 'Getting started with GitHub Marketplace' to learn more about listing your app on GitHub Marketplace.
To learn more about how users can install your app from GitHub Marketplace, see 'Purchasing and installing apps in GitHub Marketplace' in the GitHub Help documentation.
Allowing people to install your public app on their repository
You can enable others to install your public app by providing the installation URL in places like your app's homepage. You can then point to your app's homepage from the landing page on GitHub.
If you are migrating from an OAuth App to a GitHub App, you can use query parameters to preselect the repositories and account when installing the GitHub App. See 'Migrating OAuth Apps to GitHub Apps' to learn more.
These steps assume you have built a GitHub App: App bouncing on mac os.
Authorizing users during installationGithub Download Zip
You can simplify the authorization process by completing it during app installation. To do this, select Request user authorization (OAuth) during installation when creating or modifying your app in GitHub. See 'Creating a GitHub App' to learn more.
Once someone has installed your app, you will need to get an access token for the user. See steps 2 and 3 in 'Identifying a users on your site' to learn more.
Preserving an application state during installation
You can provide a
state parameter in an app's installation URL to preserve the state of the application page and return people back to that state after they install, authenticate, or accept updates to your GitHub App. For example, you could use the state to correlate an installation to a user or account.
To preserve a state, add it to the installation URL: Remove app from mac startup.
https://github.com/apps/<app name>/installations/new?state=AB12t
Apps on GitHub allow you to automate and improve your workflow. You can build apps to improve your workflow. You can also share or sell apps in GitHub Marketplace. To learn how to list an app on GitHub Marketplace, see 'Getting started with GitHub Marketplace.'
GitHub Apps are the officially recommended way to integrate with GitHub because they offer much more granular permissions to access data, but GitHub supports both OAuth Apps and GitHub Apps. For information on choosing a type of app, see 'About apps' and 'Differences between apps.'
If you are using your app with GitHub Actions and want to modify workflow files, you must authenticate on behalf of the user with an OAuth token that includes the
workflow scope. The user must have admin or write permission to the repository that contains the workflow file. For more information, see 'Understanding scopes for OAuth apps.'
For a walkthrough of the process of building a GitHub App, see 'Building Your First GitHub App.'
Requesting support
For questions, bug reports, and discussions about GitHub Apps, OAuth Apps, and API development, explore the GitHub API Development and Support Forum. The forum is moderated and maintained by GitHub staff, but questions posted to the forum are not guaranteed to receive a reply from GitHub staff.
Consider reaching out to GitHub Support directly using the contact form for:
Github Desktop Client
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |