[
https://issues.apache.org/jira/browse/OOZIE-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17651199#comment-17651199
]
Andras Salamon commented on OOZIE-3479:
---------------------------------------
I wanted to eliminate release-log.txt a while back because `git log --oneline`
contains almost the same info, at least for the latest releases. But I was
convinced that in some special cases it is useful. I'm not sure if an automatic
update can handle cases like that. I assume we can read most of the info from
the Jira (number, description), but how can we add the {{(jmakai via
dionusos)}} part automatically?
In solr, committers usually ask the pull request creators to add modifications
to the CHANGE.txt (The solr variant of release-log.txt). But of course it can
cause git conflicts, misunderstandings... Sometimes committers add this info
manually before they merge the change. Of course it is easy to forget.
> Build pre-commit pipeline for pull requests.
> --------------------------------------------
>
> Key: OOZIE-3479
> URL: https://issues.apache.org/jira/browse/OOZIE-3479
> Project: Oozie
> Issue Type: Task
> Reporter: Gézapeti
> Priority: Major
>
> I think it would be great to accept pull requests for Oozie as well.
> We should build the pre-commit system out first to see how it works for us
> before updating the site and changing the rules.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
