Providing instructions for self hosted solutions

[James712346]

When running this action in gitea, or another CI/CD based off github action, this will produce a ::error::Bad credentials error. Therefore this can be fixed by setting local environment, INPUT_TOKEN, to a user generated GitHub token key

[CLAassistant]

All committers have signed the CLA.

[James712346]

Image showing the action now working with the environment set

[per1234]

Thanks for your PR @James712346!

The standard approach for setting the token is to use the action's token input:

setup-arduino-cli/action.yml

Line 8 in d0811f7

token:

Unfortunately the action's author never wrote user friendly documentation of the inputs so currently the user would need to study the action.yml metadata file to learn of the existence of this input.

Rather than document the input in the context of this specific use case, it will be better to instead provide a general reference to the action's inputs. This information will be applicable to all contexts. You can use the inputs documentation of this similar action as a model for how to write the documentation in the standardized format used in Arduino's GitHub Actions actions:

https://github.com/arduino/setup-task/blob/main/README.md?plain=1#L18

[James712346]

Haha, I did look at action.yaml when debugging this issue and missed that definition, and didn't even think about, INPUT_TOKEN would be defined in there. At the time I thought it was pretty weird, to have gitHub.token as INPUT_TOKEN in the js code. But it all makes sense now

To be fair to me, I was pretty tried when I did this