When setting up a new repo to release, from gonzo requires you to set the project config in the repo gonzo config --project=Foo. However since this is a one off task it is easy to forget about it. Since the project name is tied to the repo anyway is there any reason why there can't be a .gonzo file in the repo that contains the project config (and any other project specific config) so that this step is unnecessary?
When setting up a new repo to release, from gonzo requires you to set the project config in the repo
gonzo config --project=Foo. However since this is a one off task it is easy to forget about it. Since the project name is tied to the repo anyway is there any reason why there can't be a.gonzofile in the repo that contains the project config (and any other project specific config) so that this step is unnecessary?