allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Igor Bondarenko" <jetmi...@gmail.com>
Subject [allura:tickets] Re: #7836 Merge request shows 0 commits, if upstream has new commits
Date Tue, 10 Mar 2015 07:44:17 GMT
Yeah, I think current behavior makes sense if we can update merge request, but we should make
it more obvious to the user that such possibility exists


---

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

**Status:** in-progress
**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.
Mime
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message