Closed chasinglogic closed 6 months ago
You'll need to setup a github token and add it to the project secrets for this to work. You can find instructions for that here and here:
You'll need to setup a github token and add it to the project secrets for this to work. You can find instructions for that here and here:
* https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-fine-grained-personal-access-token * https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions#creating-secrets-for-a-repository
Actually GITHUB_TOKEN is set automatically, I think it already has access to the release api. Guess it's easy to find out by trying.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 83.03%. Comparing base (
ecd068f
) to head (70f3e99
). Report is 7 commits behind head on master.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
This adds a continuous delivery pipeline which will run on release tags. It currently will build a release binary for Linux x86_64, Linux ARM, and MacOS x86_64 (which can be run on M* series macs).
It has code in it already to support cross compiling using cross which can be setup later. I've yet to get it working flawlessly on my own projects so I have left the setup code in but not utilised it.
This fixes https://github.com/altsem/gitu/issues/50