coop-cloud/uptime-kuma
0
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

setup maintenance for repo #9

Merged
stevensting merged 6 commits from maintainer into main 2026-04-01 15:08:41 +00:00
Conversation 5 Commits 6 Files Changed 4 +35 -4
stevensting commented 2026-03-31 16:00:36 +00:00
Owner
Copy Link
No description provided.
❤️ 1
stevensting added 2 commits 2026-03-31 16:00:36 +00:00
rework recipe and upgrade kuma version 773fdeb412
adding information for maintainership f41d89d320
stevensting added 1 commit 2026-03-31 16:07:31 +00:00
Revert "rework recipe and upgrade kuma version" 7897cae890 
This reverts commit 773fdeb412.
stevensting commented 2026-03-31 16:39:05 +00:00
Author
Owner
Copy Link

Call for co-maintainers @kawaiipunk @knoflook @cas @3wordchant

also feel free to look at #8

Call for co-maintainers @kawaiipunk @knoflook @cas @3wordchant also feel free to look at #8
stevensting added 1 commit 2026-03-31 16:47:49 +00:00
add pull request template 564441ab06
fauno reviewed 2026-03-31 20:25:37 +00:00
renovate.json Outdated
@ -0,0 +2,4 @@
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": [
"config:recommended"
]
fauno commented 2026-03-31 20:25:37 +00:00
Owner
Copy Link

you can add maintainers as automatic reviewers, we tried with a team on vaultwarden but it didn't work

you can add maintainers as automatic reviewers, we tried with a team on vaultwarden but it didn't work
👀 1
stevensting commented 2026-04-01 06:16:27 +00:00
Author
Owner
Copy Link

Interesting. But does it work with single user accounts?

Interesting. But does it work with single user accounts?
fauno commented 2026-04-01 14:45:33 +00:00
Owner
Copy Link

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

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
fauno reviewed 2026-03-31 20:26:12 +00:00
README.md
@ -7,2 +10,2 @@
* **Category**: Apps
* **Status**: 0
* **Maintainer**: [@stevensting](https://git.coopcloud.tech/stevensting)
* **Status**: `stable`
fauno commented 2026-03-31 20:26:12 +00:00
Owner
Copy Link

wasn't this a number from 0 to 5?

wasn't this a number from 0 to 5?
stevensting commented 2026-04-01 06:24:32 +00:00
Author
Owner
Copy Link

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!

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!
stevensting commented 2026-04-01 06:25:23 +00:00
Author
Owner
Copy Link

or do I misinterpret the term score? Can score also be a string?

or do I misinterpret the term score? Can score also be a string?
decentral1se commented 2026-04-01 07:22:48 +00:00
Owner
Copy Link

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!

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!
fauno reviewed 2026-03-31 20:27:02 +00:00
README.md
@ -1,11 +1,16 @@
# uptime-kuma
> One line description of the recipe
[![Build Status](https://build.coopcloud.tech/api/badges/coop-cloud/uptime-kuma/status.svg)](https://build.coopcloud.tech/coop-cloud/uptime-kuma)
fauno commented 2026-03-31 20:27:02 +00:00
Owner
Copy Link

nice! but i think the ci fails often and it can be misleading :P

nice! but i think the ci fails often and it can be misleading :P
👍 1
fauno reviewed 2026-03-31 20:28:28 +00:00
.gitea/PULL_REQUEST_TEMPLATE.md Outdated
@ -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)
fauno commented 2026-03-31 20:28:28 +00:00
Owner
Copy Link

should this checklist have an "I have ran abra recipe lint" item?

should this checklist have an "I have ran `abra recipe lint`" item?
👀 1
stevensting commented 2026-04-01 06:28:15 +00:00
Author
Owner
Copy Link

good idea

good idea
stevensting added 1 commit 2026-04-01 06:34:00 +00:00
added recipe linting 1876e3555d
stevensting added 1 commit 2026-04-01 14:53:30 +00:00
add standard reviewer ea9e14c357
stevensting merged commit 31a4e77938 into main 2026-04-01 15:08:41 +00:00
stevensting deleted branch maintainer 2026-04-01 15:08:41 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
3wordchant aadil abra-bot ammaratef45 Apfelwurm appletalk arjan basebuilder Brooke carla cas codegod100 coopcloud cyrnel decentral1se devydave fauno flancian Frando iexos jade javielico jjsfunhouse jmakdah2 joe-irving kawaiipunk knoflook kolaente lambdabundesverband linnealovespie marlon mayel mirsal moosemower moritz nicksellen notplants p4u1 pau pharaohgraphy PhiNatalie renovate-bot ripclap rix rscmbbng sef simon sixsmith stevensting tobias trav val vaznasty virtualboys wolcen wykwit xynosis yksflip
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/uptime-kuma#9
No description provided.
Delete Branch "maintainer"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?