GitLoad - The release portal

• No registration: You can use our product for any public GitHub repository. Just append /username/repository to the URL. There's no need for prior coordination regardless of project size or release interval.
• Maintenance free: Your releases will appear on GitLoad automatically and instantly. No changes to your workflow are required at all.
• Wide range of systems supported: GitLoad supports many browser and system combinations. Our website is mobile friendly too.
• Large scale repository support: Gitload is designed to be able to handle a massive number of concurrent users. It supports repositories with a virtually unlimited number of files.
• Privacy in mind: Your release data does not pass through our server at any point. We do not see and/or modify the releases the user accesses and downloads. We support a "privacy enhanced" URL mode that stops the repository name from showing up in the server logs. You can enable this by using # in the URL. Example: https://gitload.org#github/docs.
• Simple version selection: By default, we select the most recent stable release if available. Old versions and pre-releases are shown in a different color. We show the last 30 releases.
• Operating system detection: We detect the operating system of the client and highlight the downloads that most likely fit.
• Release notes display: We display the release notes below the download links in the same way GitHub does. This includes GitHub specific features like issue mentioning (#123) or user mentions (@User).
• Completely free: Free to use, free from ads, free from tracking scripts.
• Made for users to understand: We hide the source code downloads by default. Downloads for different operating systems are dark-grey colored as opposed to the light blue recommended link to discourage downloading the wrong file. Download buttons are big and contain the information the user most likely wants. We show the number of downloads on each button to make the selection for the user easier. Buttons are sorted with the most common download at the start of the list.

Requirements for users

Visitors to gitload need a somewhat modern browser with JavaScript enabled.

Requirements for a repository

• It must be public
• It must have at least one release. note that tags on their own are not considered releases

Creating a release

Creating a release is simple.

1. Go to your repository at https://github.com/<user-name>/<repository-name>/releases
2. Click the "Draft a new release" button
3. Fill in the tag, name, and description
4. Attach files you want to offer for download ("binaries")

Release description

The release description is shown by GitLoad with the same formatting as GitHub would (including issues and user mentions). If your product is intended for end-users rather than developers, consider writing a small 'Installation and Usage' chapter. If the installation instructions are in a seperate file, add a link to said file in the format [Title](https://github.com/<user-name>/<repository-name>/blob/<tag>/<file-name>). It's important to specify the release tag in the URL so users get the instructions for this specific version.

Binaries

Provided your project is not supposed to be run from source, you should attach precompiled binaries.
For projects you do run from source, you want to create a zip file with the exact contents a user needs to run this. It's usually best to test this process on a machine that lacks development tools to simulate a normal user machine
If you don't attach any files, we will show the zip and tar source code links by default.