[hibernate-dev] Re: Commit messages, and keeping JIRA in synch

2020-09-29 Thread Gunnar Morling
Am Di., 29. Sept. 2020 um 13:38 Uhr schrieb Sanne Grinovero < sa...@hibernate.org>: > On Tue, 29 Sep 2020 at 12:34, Gunnar Morling wrote: > > > > Hey Sanne, > > > > > ALL commits need to start with the JIRA code which relates to the > change. > > > > Perhaps you're doing this already, so just in

[hibernate-dev] Re: Commit messages, and keeping JIRA in synch

2020-09-29 Thread Gunnar Morling
Hey Sanne, > ALL commits need to start with the JIRA code which relates to the change. Perhaps you're doing this already, so just in case: for Debezium we have a simple check of that as a GH action, failing PR builds if they contain commits whose message does not begin with "DBZ-":

[hibernate-dev] Re: Commit messages, and keeping JIRA in synch

2020-09-29 Thread Sanne Grinovero
On Tue, 29 Sep 2020 at 12:34, Gunnar Morling wrote: > > Hey Sanne, > > > ALL commits need to start with the JIRA code which relates to the change. > > Perhaps you're doing this already, so just in case: for Debezium we have a > simple check of that as a GH action, failing PR builds if they

[hibernate-dev] Commit messages, and keeping JIRA in synch

2020-09-29 Thread Sanne Grinovero
Hi all, looks like it's a good time for me to remind how we need commits managed, and their relation to JIRA tickets. When reviewing pull requests, and before merging them, please pay attention to these simple rules as it's important for long term maintenance. We need to be able to query JIRA to