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

Konrad Windszus edited comment on OAK-12257 at 6/24/26 7:15 AM:
----------------------------------------------------------------

[~reschke] Branch [https://github.com/apache/jackrabbit-oak/tree/OAK-12274] is 
15 commits behind (with respect to trunk, so misses the relevant commits). 
Please rebase/merge.

Reason: 
https://github.com/apache/jackrabbit-oak/blob/c256918b96b623ca96e833ad9850536a01033993/.github/workflows/commit-check.yml#L37


was (Author: kwin):
[~reschke] Branch [https://github.com/apache/jackrabbit-oak/tree/OAK-12274] is 
15 commits behind (with respect to trunk, so misses the relevant commits). 
Please rebase/merge.

> 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: Joerg Hoh
>            Priority: Major
>             Fix For: 2.4.0
>
>
> 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