[ 
https://issues.apache.org/jira/browse/OAK-12257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18088482#comment-18088482
 ] 

Konrad Windszus commented on OAK-12257:
---------------------------------------

Since I couldn't find any other action which allows this pattern based commit 
message validation, one option would be to write a custom action based on 
https://stackoverflow.com/questions/63619329/how-to-get-the-commit-message-in-github-actions
 just leveraging a [Shell 
action|(https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#jobsjob_idstepsshell]

> CI: Commit-Check broken
> -----------------------
>
>                 Key: OAK-12257
>                 URL: https://issues.apache.org/jira/browse/OAK-12257
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>
> In https://issues.apache.org/jira/browse/OAK-11269 there was 
> https://github.com/commit-check/commit-check-action in version 1.x introduced 
> to warn about commits not referencing a JIRA issue.
> As 1.x actions are no longer allowed by [ASF 
> policy](https://infra.apache.org/github-actions-policy.html) I upgraded to 
> the approved version 2.7 in 
> https://github.com/apache/jackrabbit-oak/commit/cf5f523e0a6a6c65264ac04b7b4ddb17b8580283.
>  However, 2.x does no longer supported custom commit message checks: 
> https://github.com/commit-check/commit-check/issues/426.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to