Skip to content

Conversation

yyolk
Copy link

@yyolk yyolk commented Apr 29, 2025

Description:
Adds an additional match configuration for any and all for matching PR titles.

If this PR is acceptable I can also add matching PR body content matching in the same way.

Related issue:

supersedes, closes #688
supersedes, closes #109
refs #55
closes #809

Check list:

  • Mark if documentation changes are required. (Included)
  • Mark if tests were added or updated to cover the changes.

@yyolk yyolk requested a review from a team as a code owner April 29, 2025 19:19
@yyolk yyolk changed the title add pr title matching feat: add pr title matching Apr 29, 2025
@yyolk yyolk force-pushed the yyolk/20250428-title-matching branch 2 times, most recently from 6921a11 to 16f0989 Compare April 29, 2025 22:30
@yyolk yyolk force-pushed the yyolk/20250428-title-matching branch from 16f0989 to 4c6fd80 Compare May 2, 2025 18:18
@cameronmeissner
Copy link

hoping this can be merged soon :)

@shadoath
Copy link

Beautiful! I would like to see this as well!

}

export function getTitle(): string | undefined {
const pullRequest = github.context.payload.pull_request;
Copy link

@2bndy5 2bndy5 Sep 10, 2025

Choose a reason for hiding this comment

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

Can we instead use REST API (octokit) to get the title dynamically?

I think the github.context may be statically set upon workflow event trigger. This would lead to confusion about using an outdated PR title after it has changed without triggering a new CI event (eg. re-running the job that uses this action after editing the PR title).

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.

Support for labeling based on PR title
4 participants