according to the [renovate docs](https://docs.renovatebot.com/configuration-options/#reviewers) you could add an array of usernames.
we tried with a team but i just realized it's a forgejo feature, not gitea!
https://git.coopcloud.tech/coop-cloud/vaultwarden/src/branch/main/renovate.json#L7
yes it was. I now took the template from the traefik recipe, as they started the maintainers concept there. I know someone wated to create a schema for this information, but it wasn't done as far as I know.
I propose that we adopt a "stable", "testing", "unstable" designation to help organise our recipes internally and present them in a clearer way externally.
but on the contrary there is the following in there:
The status score and README of the project should be kept up to date with relevant infomation
yes it was. I now took the template from the traefik recipe, as they started the maintainers concept there. I know someone wated to create a schema for this information, but it wasn't done as far as I know.
And according to https://docs.coopcloud.tech/federation/resolutions/passed/025/
> I propose that we adopt a "stable", "testing", "unstable" designation to help organise our recipes internally and present them in a clearer way externally.
but on the contrary there is the following in there:
> The status score and README of the project should be kept up to date with relevant infomation
@decentral1se come for help!
Yeh, we're still deep in a custom README.md format 😅 I am not sure, was the stable/testing/etc. supposed to replace the numbering or be an additional metadata? Uhm... wanna ask around? Good that we ran into this!
https://docs.coopcloud.tech/abra/recipes/#status-features-score
Yeh, we're still deep in a custom `README.md` format 😅 I am not sure, was the stable/testing/etc. supposed to replace the numbering or be an additional metadata? Uhm... wanna ask around? Good that we ran into this!
* [ ] I have [updated relevant versions in `abra.sh`](https://docs.coopcloud.tech/maintainers/upgrade/#updating-versions-in-the-abrash)
* [ ] I have made my environment variable changes [backwards compatible](https://docs.coopcloud.tech/maintainers/upgrade/#backwards-compatible-environment-variable-changes)
* [ ] I have added a [release note entry](https://docs.coopcloud.tech/maintainers/upgrade/#creating-new-release-notes)
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.
Call for co-maintainers @kawaiipunk @knoflook @cas @3wordchant
also feel free to look at #8
@@ -0,0 +2,4 @@"$schema": "https://docs.renovatebot.com/renovate-schema.json","extends": ["config:recommended"]you can add maintainers as automatic reviewers, we tried with a team on vaultwarden but it didn't work
Interesting. But does it work with single user accounts?
according to the renovate docs you could add an array of usernames.
we tried with a team but i just realized it's a forgejo feature, not gitea!
https://git.coopcloud.tech/coop-cloud/vaultwarden/src/branch/main/renovate.json#L7
@@ -7,2 +10,2 @@* **Category**: Apps* **Status**: 0* **Maintainer**: [@stevensting](https://git.coopcloud.tech/stevensting)* **Status**: `stable`wasn't this a number from 0 to 5?
yes it was. I now took the template from the traefik recipe, as they started the maintainers concept there. I know someone wated to create a schema for this information, but it wasn't done as far as I know.
And according to https://docs.coopcloud.tech/federation/resolutions/passed/025/
but on the contrary there is the following in there:
@decentral1se come for help!
or do I misinterpret the term score? Can score also be a string?
https://docs.coopcloud.tech/abra/recipes/#status-features-score
Yeh, we're still deep in a custom
README.mdformat 😅 I am not sure, was the stable/testing/etc. supposed to replace the numbering or be an additional metadata? Uhm... wanna ask around? Good that we ran into this!My take:
StatustoFeaturesStatus@@ -1,11 +1,16 @@# uptime-kuma> One line description of the recipe[](https://build.coopcloud.tech/coop-cloud/uptime-kuma)nice! but i think the ci fails often and it can be misleading :P
@@ -0,0 +13,4 @@* [ ] I have deployed and tested my changes* [ ] I have [updated relevant versions in `abra.sh`](https://docs.coopcloud.tech/maintainers/upgrade/#updating-versions-in-the-abrash)* [ ] I have made my environment variable changes [backwards compatible](https://docs.coopcloud.tech/maintainers/upgrade/#backwards-compatible-environment-variable-changes)* [ ] I have added a [release note entry](https://docs.coopcloud.tech/maintainers/upgrade/#creating-new-release-notes)should this checklist have an "I have ran
abra recipe lint" item?good idea