We use a commit-msg hook on our GitHub server to enforce that all commit messages start with a JIRA ticket number from our issue tracking system. Is it possible to implement such a hook on our Looker server in order to prevent local commits from being created that will fail when Looker tries to push the developer branch to origin?
Already have an account? Login
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Thanks for your question. At this time there’s no functionality in Looker that will allow you to check the contents of the commit message box before sending out the commit. Happy to communicate to the product team that you’d like this ability for a future release of Looker.
Yes, please do. For now, when one of our developers makes a commit without a JIRA ticket number, their only recourse is to ‘Revert to Production’ to delete the local commit, losing all their changes in the process.
Hi, any plans on making this possible?