Skip to content
← SQL Source Control

How can we improve SQL Source Control?

SQL Source Control

Categories

JUMP TO ANOTHER FORUM

(thinking…)

SQL Source Control Git Hook check causing commits failure is resulting in improper object commits

I created a Git hook to check the commit message format, when i place an improper commit message it fails to commit and then when i check for pending changes again I cant find those objects which failed causing an error due to commit message. How to resolve and get back my changes to be in place to commit.

1 vote
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
ajay shared this idea  ·   ·  Report…  ·  Admin →
declined  ·  fiona.gazeley responded  · 

I’m closing this request due to inactivity. If you still require assistance with this issue please can you email support@red-gate.com. Many thanks.

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Patrick Ortuso commented  ·   ·  Report

    If I forget to add a commit message in Redgate, our GIT source control requires a commit message so Redgate reports the "Empty Git Message Error", yet the changes are saved in the repository file. A refresh of the Redgate commit tab will not show these objects anymore but when you launch GITHUB it reports the object files in question were changed and needs to be commited.

  • AdminJames Billings (Admin, Redgate) commented  ·   ·  Report

    If the commit failed, then the objects should still be on the commit tab. One possibility is that they were successfully updated in the Working Base folder (in which case, unlinking the DB, restarting SSMS and then linking again should make them reappear).
    Other than that, this is probably something you should contact our support team about so they can investigate in more depth (you can email support@red-gate.com)