Edgewall Software

Changes between Version 1 and Version 2 of Ticket #11630, comment 13


Ignore:
Timestamp:
Jun 4, 2014, 12:23:24 AM (10 years ago)
Author:
Ryan J Ollos

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #11630, comment 13

    v1 v2  
    66> My problem is not about updating a repo or notifications.  It's specifically related to a ticket update when the command is the last item in the description with no extra characters after the ticket number.
    77
    8 In comment:6 I showed cases in which the tickets were not being updated even when there were trailing characters after the ticket number. I doubt the issue is due to CommitTicketUpdater failing to parse the ticket reference from the commit message. I am even less convinced that it has anything to do with the message not having any trailing characters. If you still believe this, how can you explain the cases shown in comment:6?
     8In comment:6 I showed cases in which the tickets were not being updated even when there were characters after the ticket number. I doubt the issue is due to CommitTicketUpdater failing to parse the ticket reference from the commit message. I am even less convinced that it has anything to do with the message not having any characters after the ticket reference (and you seemed to agree in comment:8). If you still believe this, how can you explain the cases shown in comment:6?
    99
    1010You should try executing your `post-receive` hook from the command line, passing in a changeset hash for a case in which the message didn't get inserted, and another case in which the message did get inserted.