Forked repos receive multiple github updates when a commit is shared
Reported by Lee Henson | May 21st, 2008 @ 06:21 AM
Scenario:
UserA and UserB both use the same lighthouse project.
UserA's GitHub RepoA is forked by UserB into RepoB.
UserA works on a lighthouse ticket #99, and commits and pushes the work to RepoA with [#99] in the commit message.
UserA suggests UserB should pull in that commit as it affects UserB's work.
RepoA is merged into RepoB and UserB pushes the merge commit to RepoB.
Ticket #99 in Lighthouse now has two github-generated comments, one from UserA and one from UserB. The SHA1 commit hashes mentioned in the comments are different. UserA receives an email about UserB's comment on #99.
Would it be possible to do some sort of textual comparison of the commit message and not apply any commit message which is generated by GitHub if the exact same commit message already exists in the comments?
Comments and changes to this ticket
-
Will June 3rd, 2008 @ 04:22 PM
- → State changed from “new” to “open”
- → Assigned user changed from “” to “rick”
-
rick June 4th, 2008 @ 08:15 PM
- → State changed from “open” to “invalid”
Hey, this is for Github, not Lighthouse :)
-
Lee Henson June 5th, 2008 @ 02:17 AM
Pffft. They might say the opposite! I'll post it there instead.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Using Lighthouse to track Lighthouse.
