Post-commit lighthouse ticket updates being posted as wrong user

Morgan Schweers's Avatar

Morgan Schweers

22 Apr, 2008 02:04 AM

Greetings, It appears that whenever I post a fix for a bug that someone else reported, the 'fix' message that gets added onto the bug report is listed as if it was written by the original author of the bug, or perhaps the last commenter?

Examples are here, there, and everywhere

And one more...

Any ideas what's going on?

It should be posting as me, but I'm not sure how to make it do that, or what I did to do that wrong... There are some other bugs where it seems to have worked.

Hope this helps, or you can tell me what I'm doing wrong. Thanks muchly!

-- Morgan Schweers, CyberFOX!

  1. 1 Posted by Rick on 22 Apr, 2008 08:53 PM

    Rick's Avatar

    Whoa that is odd. I'm assuming this is from a git or svn post commit hook? What user does the token belong to?

  2. 2 Posted by Morgan Schweers on 22 Apr, 2008 09:20 PM

    Morgan Schweers's Avatar

    Greetings, Actually it's a Warehouse hook (Lighthouse Beacon)...

    It belongs to my Lighthouse user account. It's listed as:

    bq. All Projects / Warehouse Integration / R & W

    in my account profile ( http://jbidwatcher.lighthouseapp.com/users/13969 )

    -- Morgan Schweers, CyberFOX!

  3. 3 Posted by carpeaqua on 22 Apr, 2008 11:33 PM

    carpeaqua's Avatar

    I'm also having this issue, but my repositories are hosted at Beanstalk. Any suggestion for how to resolve it would be great.

  4. 4 Posted by rq on 09 May, 2008 12:54 AM

    rq's Avatar

    +1, coming from github it appears the news feed correctly lists the commit as coming from me (my token) but the ticket itself displays the original reporter as the commit owner.

  5. 5 Posted by Rick on 09 May, 2008 06:59 PM

    Rick's Avatar

    These are issues with the external services not using our API correctly. If you only send Lighthouse just one token, there's not much Lighthouse can do about it. We get around this on the Rails github/lighthouse accounts by setting up a 'Repository' dummy user.

  6. 6 Posted by Morgan Schweers on 11 May, 2008 09:08 PM

    Morgan Schweers's Avatar

    Greetings, Okay, since I'm going from a Warehouse hook, what should it be doing differently than the standard code?

    -- Morgan Schweers, CyberFOX!

  7. 7 Posted by pete on 23 Jan, 2009 02:42 AM

    pete's Avatar

    This seems to be happening again, and coming from GitHub.

    Reg Braithwaite's commits to our project are showing up in our LH feed as being committed by me. Flattering but highly inaccurate! :)

    Is there an obvious place where Reg can set up his own LH key on GitHub?

  8. 8 Posted by Will Duncan on 23 Jan, 2009 03:12 AM

    Will Duncan's Avatar

    Pete, please see Ricks last reply:

    These are issues with the external services not using our API correctly. If you only send Lighthouse just one token, there's not much Lighthouse can do about it. We get around this on the Rails github/lighthouse accounts by setting up a 'Repository' dummy user.

    We use an additional user to create the key, so it acts like a bot.

  9. brandi closed this discussion on 29 Jun, 2012 10:06 PM.

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