Skip to content

ci: post sticky comment on invalid PR title - #128

Merged
kodiakhq[bot] merged 2 commits into
mainfrom
ci/sticky-pr-title-comment
Nov 16, 2026
Merged

kodiakhq[bot] merged 2 commits into
mainfrom
ci/sticky-pr-title-comment

Conversation

@RedStar071

@RedStar071 RedStar071 commented Nov 16, 2026 •

Copy link
Copy Markdown
Member

🔗 Linked issue

None.

🧭 Context

A failed title check only shows a red status. Contributors do not see the reason unless they open the run. The same sticky comment already works in redstar071.dev.

📚 Description

Adds the Semantic Pull Requests workflow. It checks the PR title against Conventional Commits and posts a sticky comment when the title is invalid. The comment is removed once the title is valid.

🤖 AI disclosure: Wolfstar Agent Kit modified this description. AI open source policy.

RetriggerView in GreptileConfidence Score: 5/5

The PR appears safe to merge.

Reviews (2) · Last reviewed commit: "ci: format semantic pull request workflo..." · Reviewed by Greptile

Explain a failed title check in the pull request, like redstar071.dev. The comment goes away once the title is valid.
@coldtea-pr-lens

Copy link
Copy Markdown

Note

The title starts with ci:, so PR Lens left this pull request undrawn. Comment @pr-lens draw to draw it

github.comment.notice: false in .github/pr-lens.yml turns this note off

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes — the single new workflow file in this PR.

  • Semantic Pull Requests workflow — validates the PR title on pull_request_target (opened, edited, synchronize) with amannn/action-semantic-pull-request, using a lowercase-subject subjectPattern.
  • Sticky comment on failure — marocchino/sticky-pull-request-comment posts the lint error under the pr-title-lint-error header. A later step deletes it once the title is valid.
  • Security posture — both actions are SHA-pinned and nothing from the PR is checked out, so pull_request_target is safe here. Top-level permissions: {} is narrowed to contents: read, pull-requests: write and statuses: write on the job. error_message is only passed as an action input, not interpolated into a shell script.

Pullfrog  | View workflow run | Using claude-sonnet-5-5 | 𝕏

greptile-apps[bot]
greptile-apps Bot previously approved these changes Nov 16, 2026
@greptile-apps
greptile-apps Bot dismissed their stale review November 16, 2026 19:30

Dismissed because a newer commit was pushed; Greptile will re-review the current head.

@kodiakhq
kodiakhq Bot merged commit 7410220 into main Nov 16, 2026
11 checks passed
@kodiakhq
kodiakhq Bot deleted the ci/sticky-pr-title-comment branch November 16, 2026 19:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant