+1 to Dan's points. [GEODE-XYZ] OR [DOCS] [WEBSITE] would be valid "tags" and could then still be part of a hook to enforce proper formatting as well...
On Mon, Feb 29, 2016 at 11:05 AM, Dan Smith <[email protected]> wrote: > My opinion is that docs and minor changes to tests or build scripts don't > need necessarily a JIRA. So I'm not sure we want to enforce this with a > hook. > > That said, I definitely see commits in the log that look like product bug > fixes, and I totally agree those should have ticket #s in the commit. > > Jason suggested something that I think might be a good idea - for changes > that don't need a JIRA, maybe we can put some other tag in that spot. For > example: > > DOCS: Update most occurrences of "Geode" to "Apache Geode". > > -Dan > > On Fri, Feb 26, 2016 at 6:34 PM, kareem shabazz <[email protected]> > wrote: > > > Is it by design that there are no client-side Git hooks to prevent this > > sort of thing? > > > > -- > > Kareem > > > > > > > > > > On Fri, Feb 26, 2016 at 10:36 AM -0800, "Kirk Lund" <[email protected]> > > wrote: > > > > > > > > > > > > > > > > > > > > > > Please remember to include the GEODE-xxx jira ticket # in your commit > > messages. I'm looking at git log on develop and I can't correlate several > > checkins with any jira tickets. > > > > Thanks, > > Kirk > > > > > > > > > > > > > -- ~/William
