The configure button doesn’t exist anywhere until AFTER
you have installed Render into a specific repository.
It is actually not at all obvious why this install into a specific repository, as opposed to authorizing Render to have access to your github account–which is absolutely necessary. If you don’t do this per repository install thing, you get a message that Render can’t connect to your repository. Then, Render merrily clone the repository, does the build, uploads and everything is perfect.
So, in addition to documentation it seems like you need to think through what the extra step does and why it is even needed.
So, then clicking configure provides a way to:
- choose specific permissions that Render has
- choose one or more repo’s that Render is installed into (which really means can see and access to clone)
- revoke or suspend access for Render
A few problems: it doesn’t help the user to be able to choose/set the specific permissions because you know what you need and that’s what you need and you shouldn’t request more. But even if I don’t do this step Render can do the minimal thing it needs, which is to clone the repo.
it seems you can do all of this from the global settings option of your github account.
So, much ado about nothing to get rid of a log message, which is harmless anyway.
Or so it seems to me (I may be wrong) because everything worked as expected, except for the log message, without performing the configure step.