Is your feature request related to a problem? Please describe.
Having the PR workflow in the clio repository is proving to be more trouble than it's worth.
In many cases, you need to provide unique API keys to Github in order to execute integration tests.
Calling the workflow remotely means these processes need to be updated in there for everything.
This is a combinatorial explosion that is not worth maintaining.
Describe the solution you'd like
Just have the PR workflow live in the template.
The automated update workflow issue generation is the only one that needs to be remove.
Is your feature request related to a problem? Please describe.
Having the PR workflow in the
cliorepository is proving to be more trouble than it's worth.In many cases, you need to provide unique API keys to Github in order to execute integration tests.
Calling the workflow remotely means these processes need to be updated in there for everything.
This is a combinatorial explosion that is not worth maintaining.
Describe the solution you'd like
Just have the PR workflow live in the template.
The automated update workflow issue generation is the only one that needs to be remove.