Lighthouse Users

Comments and changes to this ticket

• 

  Justin Palmer April 15th, 2008 @ 04:10 PM

  • → Milestone changed from “” to “Phase Deuce”
• 

  rick May 1st, 2008 @ 08:08 PM

  It has to do with the way we parse the changeset tags. They were written from subversion usage and meant to go at the end of the message. However, github adds the github url to the end. I was going to actually update the github LH poster to put the url above the message, but git also lets you add attributes like "Signed-off-by". Because of this, I'll change the way changesets are parsed.

• 

  Will May 1st, 2008 @ 08:13 PM

  • → State changed from “new” to “open”
• 

  Michael Bleigh May 4th, 2008 @ 01:29 AM

  +1 to this, been driving me crazy!

• 

  Eirik Dentz Sinclair June 11th, 2008 @ 03:23 PM

  As of June 11th, I have a similar, probably related issue. Changing the ticket state in the git commit message works for me, but the using responsible:user does not. I'm a little unclear on if I need to quote the username value if it contains spaces, but it has failed to update for me with and without quoted values for responsible and for usernames without any spaces in them.

• 

  Ry July 19th, 2008 @ 02:38 PM

  • → Tag changed from “” to “api”
  • → State changed from “open” to “invalid”

  Just wanted to add a +1 to Erik's comment above. We've been having some headaches related to commit hooks.

  State changes work fine in github commit messages, but responsible does not. Is this still an open issue (unclear since the original description for the ticket seems to work) or is it a problem in my formatting? What values are acceptable for responsible? Username, email, display name?

  To sum up:

  Using [#1234 state:invalid responsible:foobar] will correctly change the state, but will not change the user that is responsible.

• 

  Ry July 19th, 2008 @ 02:58 PM

  • → State changed from “invalid” to “open”

  Hmmm, it appears my comment changed the state of this ticket.

  [#1234 state:open]

• 

  Morgan Schweers July 22nd, 2008 @ 12:46 AM

  Greetings,

  For reference, the problem exists for svn commits also.

  I can tag items, but setting the state fails, at least when included with a tagged:something entry... I haven't tried putting only the state change in the lighthouse annotation yet.

  -- Morgan

• 

  Morgan Schweers October 29th, 2008 @ 10:32 AM

  • → Tag changed from “api” to “api committed”

  +1

  I have this issue with SVN as well. It does not matter what order I put the options in. [HASHNUMBERHERE state:resolved tagged:committed responsible:jlee milestone:none]

  [HASHNUMBERHERE state:resolved]

  [HASHNUMBERHERE tagged:committed state:resolved responsible:jlee milestone:none]

  etc. They all change the tag (the obvious ones) but none change the state or responsible options. I can change both of these directly in the comments.

  HASHNUMBER is used in place of number to prevent changing any tickets here.