Hi Folks.
This is about rights to configure
I currently have rights to neither settings. If I wanted to add something like Automate the create_readme script and issue creation, I would need these rights.
Do we have a process on who has these rights? On how to obtain them?
If yes, could we define one. Also could I have them? If yes, I would write the automation for the above step.
It’s informal. Initially only @aschrijver and @weex had those rights, now I have them too.
I added you to the administrators team. Can you access repository settings now?
Thanks. I’ve now created:
This should automate most FEP facilitators tasks.
cc @fep.hosts
Just so that everyone is informed.
I’ve merged the pull request. Getting it to work was harder than expected. A bug in the configuration arose due to one needing the private key in CI ending in a new line.
Another thing, I just discovered
this means that currently, we need to approve the CI job if somebody submits a FEP. Is this the state we want?
Link to woodpecker settings: Woodpecker
Is manual approval required for every CI job, including on-push checks? In this is the case, I would prefer to not have it, because in my opinion automatic on-push checks have greater utility.
I changed it to no permission for now.
If there are any effects, please comment here.
No issues so far.
What are the consequences of changing it to no permission? The description says “This setting can be dangerous and is only recommended for private instances.” But what do they mean by “dangerous”?
