Skip to content

Conversation

@dgunzy
Copy link

@dgunzy dgunzy commented Feb 8, 2026

Signed-off-by: Daniel Guns danbguns@gmail.com

@dgunzy dgunzy force-pushed the gitea-pr-comment branch 2 times, most recently from e29ca71 to c4343dc Compare February 8, 2026 14:20
Copy link
Member

@matheuscscp matheuscscp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks very for the contribution!

Signed-off-by: Daniel Guns <danbguns@gmail.com>
@dgunzy dgunzy marked this pull request as ready for review February 8, 2026 15:35
Copy link
Member

@matheuscscp matheuscscp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 🚀

Can you please run a manual e2e test for this with a Gitea/Forgejo repo? In my PRs I tested together with ResourceSetInputProvider e2e, passing the event.toolkit.fluxcd.io/change_request annotation with << inputs.id | quote >> to a HelmRelease applied by the ResourceSet. The helm-controller will then send events to notification-controller and they must show up as the sticky comment in the Gitea/Forgejo PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants