Skip to content

deps: update camunda-platform-digests #68332

deps: update camunda-platform-digests

deps: update camunda-platform-digests #68332

name: Repo - Pull Request Conventions
on:
pull_request:
types: [opened, edited, synchronize, reopened]
push:
branches:
- 'release-please--branches--*'
permissions:
contents: read
pull-requests: read
jobs:
check:
name: Check PR Conventions
# Do NOT run PR conventions on release-please PRs.
# The required "Check PR Conventions" status is instead reported by a
# lightweight push-triggered run on release-please branches.
if: ${{ github.event_name == 'push' || !startsWith(github.head_ref, 'release-please--') }}
runs-on: ubuntu-latest
steps:
- name: Report required status for release-please branch pushes
if: ${{ github.event_name == 'push' }}
run: |
echo "Release-please branch push detected (${GITHUB_REF_NAME}); reporting required status only."
- uses: amannn/action-semantic-pull-request@48f256284bd46cdaab1048c3721360e808335d50 # v6.1.1
if: ${{ github.event_name == 'pull_request' }}
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
types: |
feat
fix
refactor
revert
test
docs
style
build
ci
cd
chore
chore(deps)
chore(release)
deps
# Configure additional validation for the subject based on a regex.
# Ensures the subject doesn't start with an uppercase character.
# Also ensures the subject doesn't contain parentheses (we don't use scope in commit titles).
subjectPattern: ^(?![A-Z])(?!.*[()]).+$
# Ignore release PR since it's different and already automated.
ignoreLabels: |
release/pr
dependencies
automation/renovatebot
# When using "Squash and merge" on a PR with only one commit, GitHub
# will suggest using that commit message instead of the PR title for the
# merge commit, and it's easy to commit this by mistake. Enable this option
# to also validate the commit message for one commit PRs.
validateSingleCommit: true
- name: Checkout
if: ${{ github.event_name == 'pull_request' }}
uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6
with:
ref: ${{ github.event.pull_request.head.sha }}
fetch-depth: 0
- name: Enforce feat/fix/refactor/docs/revert reserved for user-facing chart changes
if: ${{ github.event_name == 'pull_request' }}
env:
PR_TITLE: ${{ github.event.pull_request.title }}
BASE_REF: ${{ github.event.pull_request.base.ref }}
run: |
# feat/fix/refactor/docs/revert titles propagate to RELEASE-NOTES.md
# and artifacthub.io/changes via git-cliff (see cliff.toml
# commit_parsers). Reject them when the PR touches no user-facing
# chart files. Mirrors the git-cliff exclude-paths in the
# release-tools `release-notes` command so both layers stay in sync.
if printf '%s' "$PR_TITLE" | grep -qE '^(feat|fix|refactor|docs|revert)(\(.+\))?(!)?:'; then
user_facing=$(git diff --name-only "origin/${BASE_REF}...HEAD" \
| grep '^charts/' \
| grep -vE '^charts/[^/]+/(test/|go\.mod$|go\.sum$)' \
| wc -l | tr -d ' ')
if [ "$user_facing" -eq 0 ]; then
echo "::error::PR title uses 'feat:', 'fix:', 'refactor:', 'docs:', or 'revert:' but no user-facing files under charts/<version>/ are changed (test/, go.mod, go.sum excluded). These types propagate to release notes. Use ci:, chore:, test:, or build: instead."
exit 1
fi
fi