Do we need special types for GitOps commits ? #206

New Issue

GiteaMirror · 2026-02-17T11:53:40-06:00

GiteaMirror commented

2026-02-17 11:53:40 -06:00

Originally created by @mdufourneaud on GitHub (May 27, 2024).

In the GitOps context, the commits are also used to declare the state resources, and I am wondering if there is a mapping between the "standard" commit types and the GitOps operations, or if we need to add new types dedicated to GitOps.
In the 2nd case, here are the GitOps types I propose:

create: a commit of the type create create new resources
update: a commit of the type update update existing resources
- upgrade: a commit of the type upgrade, a special update, upgrade existing resources
delete: a commit of the type delete delete existing resources

Originally created by @mdufourneaud on GitHub (May 27, 2024). In the GitOps context, the commits are also used to declare the state resources, and I am wondering if there is a mapping between the "standard" commit types and the GitOps operations, or if we need to add new types dedicated to GitOps. In the 2nd case, here are the GitOps types I propose: * `create:` a commit of the type `create` create new resources * `update:` a commit of the type `update` update existing resources * `upgrade:` a commit of the type `upgrade`, a special update, upgrade existing resources * `delete:` a commit of the type `delete` delete existing resources

GiteaMirror referenced this issue

2026-02-17 12:00:24 -06:00

[PR #206] [MERGED] fix: Fix anchor links in Korean translation #357

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/conventionalcommits.org#206