-
Story
-
Resolution: Unresolved
-
Normal
-
None
Features
- Implement the update comment strategy for Forgejo and Gitea providers to allow in-place status updates.
https://github.com/openshift-pipelines/pipelines-as-code/commit/4c847ce886917bb4d538aeebcb87988e8a1bc2d2(https://github.com/openshift-pipelines/pipelines-as-code/commit/4c847ce886917bb4d538aeebcb87988e8a1bc2d2) - Add ForgejoSettings to the Repository CRD to support comment_strategy configuration.
https://github.com/openshift-pipelines/pipelines-as-code/commit/4c847ce886917bb4d538aeebcb87988e8a1bc2d2(https://github.com/openshift-pipelines/pipelines-as-code/commit/4c847ce886917bb4d538aeebcb87988e8a1bc2d2) - Extend provider logic and admission webhooks to validate and process Forgejo-specific comment strategies.
https://github.com/openshift-pipelines/pipelines-as-code/commit/4c847ce886917bb4d538aeebcb87988e8a1bc2d2(https://github.com/openshift-pipelines/pipelines-as-code/commit/4c847ce886917bb4d538aeebcb87988e8a1bc2d2)
Miscellaneous
- Update CRD schema documentation and configuration templates to reflect new Forgejo enum values.
https://github.com/openshift-pipelines/pipelines-as-code/commit/4c847ce886917bb4d538aeebcb87988e8a1bc2d2(https://github.com/openshift-pipelines/pipelines-as-code/commit/4c847ce886917bb4d538aeebcb87988e8a1bc2d2) - Increase unit test coverage for Forgejo update and disable_all comment strategy paths.
https://github.com/openshift-pipelines/pipelines-as-code/commit/4c847ce886917bb4d538aeebcb87988e8a1bc2d2(https://github.com/openshift-pipelines/pipelines-as-code/commit/4c847ce886917bb4d538aeebcb87988e8a1bc2d2)
Would you like me to create an image of this summary formatted for a presentation slide?