Best way to upload/deploy jar files in Github

Since 2d July 2013, you now have a new way to "upload runnable jar files for download" , through a release.

Releases, a workflow for shipping software to end users.
Releases are first-class objects with changelogs and binary assets that present a full project history beyond Git artifacts. They're accessible from a repository's homepage:

• Releases are accompanied by release notes and links to download the software or source code.
• Following the conventions of many Git projects, releases are tied to Git tags. You can use an existing tag, or let releases create the tag when it's published.
• You can also attach binary assets (such as compiled executables, minified scripts, documentation) to a release. Once published, the release details and assets are available to anyone that can view the repository.

That now replaces the old binary upload service, which was removed in December 2012.

Github used to have a download link where you could upload your binaries.

As of the end of 2012, the download option has been removed.

My personal favorite is to use source forge.

Instructions on integrating github with source forge can be found here

http://sourceforge.net/publish/?source=github

Here is an example of an arduino project that uses github for source, and source forge for binaries.

https://sourceforge.net/projects/all-spark-cube/

https://github.com/spudstud/All-Spark-Cube

You would have to include them in the repo, which is not wise because Git does best with source code, not binary files.

Perhaps a better option is to use S3 as they recommend, or Google Code.