[allura:tickets] #7836 Merge request shows 0 commits, if upstream has new commits

[Igor Bondarenko <je...@gmail.com>]

- **status**: in-progress --> review
- **Comment**:

Closed #739. `ib/7836`

ForgeHg merge request: https://sourceforge.net/p/forgehg/code/merge-requests/4/



---

** [tickets:#7836] Merge request shows 0 commits, if upstream has new commits**

**Status:** review
**Milestone:** unreleased
**Labels:** sf-4 42cc ux sf-current 
**Created:** Wed Feb 18, 2015 11:44 PM UTC by Dave Brondsema
**Last Updated:** Fri Mar 06, 2015 09:56 AM UTC
**Owner:** Igor Bondarenko

A merge request works ok if the downstream (forked) repo has all of the upstream (parent) repo's commits.  But if the upstream repo has new commits on it, then the merge request shows 0 commits.  This is because `MergeRequest._commits` can't find the upstream HEAD in the forked repo, so the `log()` doesn't work.  We should have a smarter technique for finding the list of added commits.  We should also have better error handling and message to the user when it can't be found since that'll probably still happen sometimes.


---

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.