You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Releases are GitHub's way of packaging and providing software to your users. You can think of it as a replacement to using downloads to provide software.
With Releases, you can provide links to binary files, as well as release notes describing your changes.
At their core, Releases are based on Git tags. Tags mark a specific point in the history of your project, so they're a great way to indicate a Release. Releases are ordered by a tag's date in the following way:
If it's an annotated tag, the tag object's date is used.
If it's a lightweight tag, then the commit object's date is used.
⌨️ Activity: Creating a release
On GitHub, navigate to the main page of the repository.
Under your repository name, click Releases.
Click Draft a new release.
Type a version number for your release. Versions are based on Git tags. We recommend naming tags that fit within semantic versioning.
Select a branch that contains the project you want to release. Usually, you'll want to release against your master branch, unless you're releasing beta software.
Type a title and description that describes your release.
If you'd like to include binary files along with your release, such as compiled programs, drag and drop or select files manually in the binaries box.
If the release is unstable, select This is a pre-release to notify users that it's not ready for production.
If you're ready to publicize your release, click Publish release. Otherwise, click Save draft to work on it later.
You can create releases from the GitHub user interface. Read this detailed documentation when you're ready to implement releases.
I won't respond to this issue, just close it when you are done!
The text was updated successfully, but these errors were encountered:
Using releases
Why Releases?
Releases are GitHub's way of packaging and providing software to your users. You can think of it as a replacement to using downloads to provide software.
With Releases, you can provide links to binary files, as well as release notes describing your changes.
At their core, Releases are based on Git tags. Tags mark a specific point in the history of your project, so they're a great way to indicate a Release. Releases are ordered by a tag's date in the following way:
If it's an annotated tag, the tag object's date is used.
If it's a lightweight tag, then the commit object's date is used.
⌨️ Activity: Creating a release
On GitHub, navigate to the main page of the repository.
Under your repository name, click Releases.
Click Draft a new release.
Type a version number for your release. Versions are based on Git tags. We recommend naming tags that fit within semantic versioning.
Select a branch that contains the project you want to release. Usually, you'll want to release against your master branch, unless you're releasing beta software.
Type a title and description that describes your release.
If you're ready to publicize your release, click Publish release. Otherwise, click Save draft to work on it later.
You can create releases from the GitHub user interface. Read this detailed documentation when you're ready to implement releases.
I won't respond to this issue, just close it when you are done!
The text was updated successfully, but these errors were encountered: