gitops commit koodi commit tekijän nimiin
CI Feature / Load example-gitea-env.conf to pipeline env (push) Successful in 17s
unit-tests Bats test report
CI Feature / Bats tests (push) Successful in 1m26s
acc-tests Cucumber test report
CI Feature / Cucumber tests (push) Successful in 2m16s
CI Feature / Report Summary (push) Successful in 5s

This commit is contained in:
moilanik
2026-06-27 03:09:37 +03:00
parent a8931aeca8
commit 0d28c3e865
4 changed files with 24 additions and 4 deletions
+10
View File
@@ -59,6 +59,12 @@ on:
extra_cmd:
required: false
type: string
author_name:
required: false
type: string
author_email:
required: false
type: string
env:
INPUT_FILE: ${{ inputs.file }}
@@ -70,6 +76,8 @@ env:
GITEA_API_URL: ${{ gitea.server_url }}
GIT_TAG_PREFIX: ${{ inputs.git_tag_prefix || '' }}
GITOPS_EXTRA_CMD: ${{ inputs.extra_cmd || '' }}
GIT_USER_NAME: ${{ inputs.author_name || '' }}
GIT_USER_EMAIL: ${{ inputs.author_email || '' }}
jobs:
update:
@@ -153,6 +161,8 @@ gitops-update:
When `GITOPS_EXTRA_CMD` is set, the script runs it after `yq` and stages all changes (`git add -A`) instead of only the input file — so any files generated by the extra command (e.g. `Chart.lock`, `charts/`) are included in the commit.
By default the GitOps commit is made as `gitea-ci-bot`. To use the original commit author instead, the dispatch workflow resolves it automatically from the consumer repo — no extra config needed. Just ensure the GitOps repo's `gitops-service.yaml` template has the `author_name` and `author_email` inputs and env mappings.
### 2.3 Parameters
| Input | Required | Description |