immich-app / immich-app/devtools
previews: GHA bot comment with deployment status
Nobody has claimed this yet.
- Dominant language
- HCL
- Stars
- 27
- Forks
- 10
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 37
Description
https://fluxcd.io/flux/components/notification/providers/#github-dispatch into a github actions workflow that leaves a comment, with https://fluxcd.io/flux/components/notification/alerts/ to feed it events from the preview objects.
For the first pass, just have the workflow log the payload and then exit, to work out what information is actually in there.
Have each preview include its own Alert object with metadata that links it to the PR.
Like in https://flux-iac.github.io/tofu-controller/use-tf-controller/flux-receiver-and-alert/, patch out the `kind` enum in the Alert CRD and add RBAC for the extra objects.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Flux GitHub Dispatch provider and Alerts documentation linked in the issue, then inspect the preview objects, workflow, Alert CRD, and RBAC configuration in this repository. The first pass should log the received payload and exit; done means each preview has a linked Alert object, the CRD accepts the needed kind, and the workflow can receive deployment events.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, kubernetes
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100