Secrets are good to pass… well… secrets to your workflows. What about non-secret values that you still don’t want to hardcode in your workflow?
Secrets also do not work everywhere in a workflow, only on the job/step level afaik.
My workflow uses environments with URLs. A fork that wants to run these workflow to test the deployment under a different URL now has to change the workflow file. It would be nice to have some form of repository setting for that. Any ideas how to achive that? I thought about using issues to store configuration but that would be extremely ugly.