- **status**: review --> in-progress - **Reviewer**: Dave Brondsema - **Comment**:
If merging is not allowed (`merge_allowed` method), e.g. disabled with `scm.merge.git.disabled = true` then none of this should run. When I had it disabled, and was logged in as a project admin and visited a MR it showed the "checking" message and ran the task and then was hidden after that. --- ** [tickets:#7866] Run can_merge in background, and cache results** **Status:** in-progress **Milestone:** unreleased **Labels:** merge-requests 42cc sf-current sf-2 **Created:** Tue Mar 31, 2015 07:04 PM UTC by Dave Brondsema **Last Updated:** Mon Apr 20, 2015 10:47 AM UTC **Owner:** Igor Bondarenko We do need to run merge requests as a background task, and cache the results. Mature projects with big repos take too long to compute if they are mergable. See https://forge-allura.apache.org/p/allura/tickets/7830/#f5b2 for discussion on running in background and caching. --- Sent from forge-allura.apache.org because [email protected] 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.
