Stan Hu cedbb3366b Fix API /project/:id/branches not returning correct merge status ... https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/24034 introduced a regression where only the first 20 branches were used to determine whether a branch has been merged because the pagination was applied incorrectly. Requesting the second page of branches via the API would always have the wrong merge status. We fix this by properly paginating the branches before requesting their merge status. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/56250		2019-03-30 05:20:29 -07:00
..
api	Fix API /project/:id/branches not returning correct merge status	2019-03-30 05:20:29 -07:00
assets	…
backup	…
banzai	…
bitbucket	…
bitbucket_server	…
constraints	…
container_registry	…
declarative_policy	…
flowdock	…
generators/rails/post_deployment_migration	…
gitaly	…
gitlab	Merge branch '50199-quick-actions-refactor' into 'master'	2019-03-29 14:48:01 +00:00
google_api	…
haml_lint	…
json_web_token	…
mattermost	…
microsoft_teams	…
object_storage	…
omni_auth/strategies	…
peek	…
quality	…
rouge	…
rspec_flaky	…
safe_zip	…
sentry	Handle missing keys in sentry api response	2019-03-29 14:53:40 +00:00
serializers	…
support	…
system_check	…
tasks	…
after_commit_queue.rb	…
backup.rb	…
banzai.rb	…
carrier_wave_string_file.rb	…
declarative_policy.rb	…
event_filter.rb	…
expand_variables.rb	…
extracts_path.rb	…
feature.rb	…
file_size_validator.rb	…
forever.rb	…
gitlab.rb	…
gt_one_coercion.rb	…
milestone_array.rb	…
mysql_zero_date.rb	…
static_model.rb	…
system_check.rb	…
uploaded_file.rb	…
version_check.rb	…