Gitlab Merge Request created after update to version 7 has many more commits than it should have -
after updating gitlab version 7 when creating merge request, list of commits larger expected. providing list of 1000+ commits when there should 5.
going through source code, unable find gitlab determining commits use merge request in order debug that. found following in compare_service.rb
@ loss go here.
# compare 2 branches 1 repo or between repositories # , return gitlab::compareresult object responds commits , diffs class compareservice def execute(current_user, source_project, source_branch, target_project, target_branch) # try compare branches commits list , diffs # # note: use satellite when need compare between 2 repos # because satellites slower operations on bare repo if target_project == source_project gitlab::compareresult.new( gitlab::git::compare.new( target_project.repository.raw_repository, target_branch, source_branch, ) ) else gitlab::satellite::compareaction.new( current_user, target_project, target_branch, source_project, source_branch ).result end end end
where gitlab getting sha's of commits not merged target branch?
it problem in rugged 0.21.0. updated in official repo can fix on own editing /home/git/gitlab/gemfile.lock
, searching rugged lib. update version 0.21.0 0.21.2.
run bundle install afterwards:
# mysql installations (note: line below states '--without ... postgres') sudo -u git -h bundle install --without development test postgres --deployment # postgresql installations (note: line below states '--without ... mysql') sudo -u git -h bundle install --without development test mysql --deployment
Comments
Post a Comment