[
https://issues.apache.org/jira/browse/OAK-11269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated OAK-11269:
----------------------------------
Description:
In order to enforce proper commit message prefixes as outlined in
https://jackrabbit.apache.org/oak/docs/participating.html#commits it would be
beneficial to use automated checks.
One such check is
https://github.com/marketplace/actions/gs-commit-message-checker which could be
easily integrated in the Build workflow.
TBD whether this only applies to feature branches/PRs or also to {{trunk}}.
It is possible to enforce certain [checks in
GitHub|https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks]
to succeed via {{.asf.yaml}}:
https://github.com/apache/infrastructure-asfyaml?tab=readme-ov-file#branch-protection
was:
In order to enforce proper commit message prefixes as outlined in
https://jackrabbit.apache.org/oak/docs/participating.html#commits it would be
beneficial to use automated checks.
One such check is
https://github.com/marketplace/actions/gs-commit-message-checker which could be
easily integrated in the Build workflow.
TBD whether this only applies to feature branches/PRs or also to {{trunk}}.
It is possible to enforce certain checks in GitHub to succeed via
{{.asf.yaml}}:
https://github.com/apache/infrastructure-asfyaml?tab=readme-ov-file#branch-protection
> Enforce commit message format with GHA
> --------------------------------------
>
> Key: OAK-11269
> URL: https://issues.apache.org/jira/browse/OAK-11269
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: continuous integration
> Reporter: Konrad Windszus
> Priority: Major
>
> In order to enforce proper commit message prefixes as outlined in
> https://jackrabbit.apache.org/oak/docs/participating.html#commits it would be
> beneficial to use automated checks.
> One such check is
> https://github.com/marketplace/actions/gs-commit-message-checker which could
> be easily integrated in the Build workflow.
> TBD whether this only applies to feature branches/PRs or also to {{trunk}}.
> It is possible to enforce certain [checks in
> GitHub|https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks]
> to succeed via {{.asf.yaml}}:
> https://github.com/apache/infrastructure-asfyaml?tab=readme-ov-file#branch-protection
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
