feat: add pr title matching#866
Conversation
yyolk
force-pushed
the
yyolk/20250428-title-matching
branch
2 times, most recently
from
6921a11 to
16f0989
Compare
yyolk
force-pushed
the
yyolk/20250428-title-matching
branch
from
16f0989 to
4c6fd80
Compare
|
hoping this can be merged soon :) |
|
Beautiful! I would like to see this as well! |
| } | ||
|
|
||
| export function getTitle(): string | undefined { | ||
| const pullRequest = github.context.payload.pull_request; |
There was a problem hiding this comment.
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).
|
Would love to see this feature! |
|
whats the status on this..? this seems very useful.. |
|
I'm not an admin for this project. I just reviewed the patch for undesirable behavior, which still hasn't been addressed. |
|
It seems like a useful feature. It would be great if it were available, especially when using conventional commits. |
7 participants
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: