GitHub commit not changing state.

Sixes's Avatar

Sixes

12 Jun, 2008 01:42 AM

Here is an example of my GitHub commit message I typically use.

"Made changes requested in ticket 19 [#19 tagged:qa-ready state:resolved]"

The ticket gets the new tag but the state is not changing. I am not the repo owner if that helps but I am a contributor.

  1. 1 Posted by Brian on 27 Jun, 2008 01:50 PM

    Brian's Avatar

    Have you figured this out? I'm seeing the exact same thing with a commit like:

    Updated readme for testing lighthouse integration [#1 state:resolved tagged:committed]

    All that does is set the tag. The state remains 'new'. If I commit without setting 'tagged' the state changes fine. So

    Updated readme for testing lighthouse integration [#1 state:resolved]

    updates the state OK.

  2. 2 Posted by Jacek Becela on 28 Jul, 2008 02:58 PM

    Jacek Becela's Avatar

    I have made a commit with message "Updated something [#1]" but it didn't show up in lighthouse (neither as a changeset nor an updated below the ticket #1. Then I made a commit with just a message (without referencing a ticket) and it showed up as a changeset.

    Anyone having the same problem?

Discussions are closed to public comments.
If you need help with Lighthouse please start a new discussion.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac