the team already exist with people on it, should i copy a `MAINTAINERS.md` and add you all to the `README.md` and `renovate.json`?
https://git.coopcloud.tech/org/coop-cloud/teams/monitoring-ng-maintainers
the team already exist with people on it, should i copy a MAINTAINERS.md and add you all to the README.md and renovate.json?
Yes, I think everyone from the team can be added. We just never added a MAINTAINERS.md and list in README.md.
Instead of putting people in renovate.json you can also add * @coop-cloud/monitoring-ng-maintainers to .gitea/CODEOWNERS file. That works for all PRs a team reference instead of individual account is less updating work.
> the team already exist with people on it, should i copy a `MAINTAINERS.md` and add you all to the `README.md` and `renovate.json`?
Yes, I think everyone from the team can be added. We just never added a MAINTAINERS.md and list in README.md.
Instead of putting people in renovate.json you can also add `* @coop-cloud/monitoring-ng-maintainers` to `.gitea/CODEOWNERS` file. That works for all PRs a team reference instead of individual account is less updating work.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
i'm interested/invested. @dannygroenewegen @simon?
the team already exist with people on it, should i copy a
MAINTAINERS.mdand add you all to theREADME.mdandrenovate.json?https://git.coopcloud.tech/org/coop-cloud/teams/monitoring-ng-maintainers
@coop-cloud/monitoring-ng-maintainers also the team can be pinged :D
Yes, I think everyone from the team can be added. We just never added a MAINTAINERS.md and list in README.md.
Instead of putting people in renovate.json you can also add
* @coop-cloud/monitoring-ng-maintainersto.gitea/CODEOWNERSfile. That works for all PRs a team reference instead of individual account is less updating work.ok done, also #11 needs to be merged