• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 10 subscribers
  • Views 1735 views
  • Users 0 members are here
Options
Related

Failed commit erases commit message

ClemsonTiger04

When a commit fails, why is the commit message removed? It's a real pain to have to keep putting it back when commit fails because credentials were accidently typed wrong or similar. What's the harm in leaving the entered commit message so one does not have to re-enter it?

i.e. wrong credentials are saved, type commit message, select what to commit. Get "Commit failed and changes are not applied. Contact ApexSQL-SA@!quest.com for help" 

Additionally, why does it seem like when credentials are saved, and then they change and then I go to commit and it fails due to invalid credentials that ApexSQL seems to keep trying the same wrong credentials so many times so quickly that it locks one's AD account? If it fails once, make it not try again until the user initiates it.

  • 0

    Hi! Could you please let us know if this is in ApexSQL Source Control? If so, what version of the tool are you currently using? 

    Please let us know so we can better help you.

  • 0

    If you are still having issues, please go to support.quest.com and open a case with Support for better assistance.

  • 0 in reply to nodier garcia

    I’ve run into this same frustration before—there’s nothing worse than spending time writing out a detailed commit message only for it to vanish because of a connection glitch or a failed validation. If you're still dealing with this, one thing that helped me was to get into the habit of 'pre-processing' my messages in a simple notepad or a scratchpad first. That way, if the commit fails or the tool refreshes, you aren't stuck trying to remember exactly what you wrote. It’s a bit of a manual workaround, but it definitely saves a lot of re-typing until a proper fix or an 'auto-save' feature is added to the UI!