Skip to content

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

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
Contributor

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

Reviewed the whole PR, which adds one new workflow file.

  • Semantic Pull Requests workflow: runs on pull_request_target (opened, edited, synchronize) with no checkout, permissions: {} at the top and only contents: read, pull-requests: write and statuses: write on the job.
  • Title lint: amannn/action-semantic-pull-request v6.1.2 rejects a subject that starts with an uppercase letter.
  • Sticky comment: marocchino/sticky-pull-request-comment v2.9.4 posts the error under the header pr-title-lint-error and deletes it once the title is valid.
  • Pins: both action SHAs match their v6.1.2 and v2.9.4 tags.
  • Expressions: error_message only goes through with:, never a shell, so there is no script injection. error_message != null treats an unset output as null, which is what the action's README relies on.

One optional note, not blocking. error_message repeats the raw PR title inside the triple-backtick fence. A title that contains a fence can close it early, so the rest of the title renders as markdown in a comment from the bot. The effect is cosmetic. Nobody needs to change this before merge.

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

greptile-apps[bot]
greptile-apps Bot previously approved these changes Nov 16, 2026
@github-project-automation github-project-automation Bot moved this from Todo to Review Approved in Wolfstar Nov 16, 2026
@kodiakhq
kodiakhq Bot merged commit 433623b into main Nov 16, 2026
19 checks passed
@kodiakhq
kodiakhq Bot deleted the ci/sticky-pr-title-comment branch November 16, 2026 19:32
@github-project-automation github-project-automation Bot moved this from Review Approved to Done in Wolfstar Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant