env variable available for git outh key

[Salamandastron1]

Hey!

Auto deploy configuration for Travis complete 🖖

There will be a little bit of setup necessary in to use a github oauth token. I'll link the docs below. The setup should all be here though. It will only deploy automagically on tags, which seem to be deliberately used in the repo so it should be muy bien.

https://docs.travis-ci.com/user/deployment/releases/#authenticating-with-an-oauth-token

[CLAassistant]

All committers have signed the CLA.

[umarcor]

I suggest using GitHub Actions instead, since the default GITHUB_TOKEN does already allow to upload artifacts and/or creating releases.

Ref #952 #968

[Salamandastron1]

Travis suggests making a machine user for this to work, and generating api key for via the information in the docs I linked. All for either implementation of Travis or Github actions but I was asked to keep this in scope of the current CI/CD method.

[umarcor]

Travis suggests making a machine user for this to work, and generating api key for via the information in the docs I linked. All for either implementation of Travis or Github actions but I was asked to keep this in scope of the current CI/CD method.

Yes, Travis requires explicitly generating an API key/token, and because of limited configurability of scopes, it is suggested to create a machine user. AFAIK, doing so requires to create an e-mail account for the machine user. Conversely, the GITHUB_TOKEN available in GHA by default does already have a limited scope (see https://help.github.com/en/actions/configuring-and-managing-workflows/authenticating-with-the-github_token#permissions-for-the-github_token), so creation of a machine user or a custom token is not required. Anyway, if you are constrained to use Travis, there is little you can do...

[github-actions]

This PR is being marked as stale due to a long period of inactivity