ci: add go-licenses check + Conventional Commits PR title gate #166
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/OpenSpec
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
RFC - Request For Comments
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
hermes-attempted
hermes-needs-clarification
hermes-ready
hermes-review
hermes-wip
human-required
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
agentic-forges/forgejo-mcp!166
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/166/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Two CI gates added to the PR pipeline:
1.
go-licensescheck (license-check step in go-ci task)go-licenses v1.6.0baked into release-tools imagegolang.org/x/*packages are Apache-2.0/BSD)--ignore=codeberg.org/goern/forgejo-mcpskips the repo root module itself2. Conventional Commits PR title + commit check (commit-title-check task)
commit-title-checkTekton task runs in parallel withbuild-and-test{{ body.pull_request.title }}origin/$BASE_REF..HEAD)semantic-releasesilently drops them post-merge^(feat|fix|docs|style|refactor|perf|test|ci|chore|build|revert)(\([^)]+\))?!?: .+!) and scope(scope)both acceptedWhy
semantic-releasereads individual commit titles post-merge to decide version bump. A malformed title does not error — it just gets silently skipped. This gate catches the problem before merge, not after.Verification
go-licenses checkexits 0 on current dep treeFiles changed
.tekton/tasks/commit-title-check.yaml.tekton/on-pull-request.yamlpr_title/base_refparams.tekton/tasks/go-ci.yamllicense-checkstepimage/release-tools/Containerfilego-licensesinstall + smoke checkimage/release-tools/VERSIONS.mdgo-licenses v1.6.0op1st Pipelines as Code/code-scans-fc4bt is running.
Starting Pipelinerun code-scans-fc4bt in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines code-scans-fc4bt -fop1st Pipelines as Code/on-pull-request-5j5zv is running.
Starting Pipelinerun on-pull-request-5j5zv in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines on-pull-request-5j5zv -fop1st Pipelines as Code/code-scans-fc4bt has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/code-scans-7ph9b is running.
Starting Pipelinerun code-scans-7ph9b in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines code-scans-7ph9b -fop1st Pipelines as Code/on-pull-request-2rb8x is running.
Starting Pipelinerun on-pull-request-2rb8x in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines on-pull-request-2rb8x -fop1st Pipelines as Code/on-pull-request-5j5zv
Task Statuses:
fetch-source
build-and-test
commit-title-check
Failure snippet:
task build-and-test has the status "TaskRunCancelled":op1st Pipelines as Code/code-scans-7ph9b has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/on-pull-request-2rb8x has failed.
Task Statuses:
fetch-source
build-and-test
commit-title-check
Failure snippet:
task build-and-test has the status "Failed":op1st Pipelines as Code/on-pull-request-mnxlm is running.
Starting Pipelinerun on-pull-request-mnxlm in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines on-pull-request-mnxlm -fop1st Pipelines as Code/code-scans-qsjws is running.
Starting Pipelinerun code-scans-qsjws in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines code-scans-qsjws -fop1st Pipelines as Code/code-scans-qsjws has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/on-pull-request-mnxlm has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check