Skip to content

Conversation

@reubeno
Copy link
Member

@reubeno reubeno commented Feb 5, 2026

We're planning to adopt Conventional Commits in this branch; this workflow helps guide contributors to following the guidelines.

Copy link
Contributor

@ddstreetmicrosoft ddstreetmicrosoft left a comment

Choose a reason for hiding this comment

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

some comments only, I'll leave this to Chris for approval

name: "Check PR Title"

on:
pull_request_target: # zizmor: ignore[dangerous-triggers]
Copy link
Contributor

Choose a reason for hiding this comment

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

do we need to restrict this to only PRs against tomls/base/main? We don't want this running for all PRs against the entire azl repo, right?

permissions:
pull-requests: write # Needed to post comments on PR
steps:
- uses: amannn/action-semantic-pull-request@v5
Copy link
Contributor

Choose a reason for hiding this comment

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

is this creating a dependency on an external repo? if so, we should probably clone and use our own repo/branch right?

env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

- uses: marocchino/sticky-pull-request-comment@v2
Copy link
Contributor

Choose a reason for hiding this comment

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

same question as above about external repo use?


# Delete a previous comment when the issue has been resolved
- if: ${{ steps.lint_pr_title.outputs.error_message == null }}
uses: marocchino/sticky-pull-request-comment@v2
Copy link
Contributor

Choose a reason for hiding this comment

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

same question as above about external repo use?

if: always() && (steps.lint_pr_title.outputs.error_message != null)
with:
header: pr-title-lint-error
message: |
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we also include a TL;DR on common formatting? Probably 99% of commits will want to use just a few common formats, e.g. feat:, fix:, etc.

On the conventialcommits.org page, even the Quick Summary isn't a good reference (IMHO) on the most common uses, it takes a bit of reading to see what options there are

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.

2 participants