API get commits using ref_name with revision_range
Summary
I have a tool which reads commits from the API from a specific range and it started to crash during this day and it's still not working, after further diagnosing I did found that it was related with the ref_name argument which was not accepting no longer the configuration that was being sent.
When requesting /projects/:id/repository/commits with a ref_name with a revision_range it returns {"error":"ref_name is invalid"}
API docs: https://docs.gitlab.com/ee/api/commits.html#list-repository-commits
Steps to reproduce
curl --header "Authorization: Bearer GITLAB_TOKEN" "https://gitlab.com/api/v4/projects/PROJECT_ID/repository/commits?ref_name=1dae32ff...6533077b&per_page=100"Example Project
Haven't created one, I believe it's not needed
What is the current bug behavior?
Not able to get commits between a range of commit sha's
What is the expected correct behavior?
Able to get commits between a range of commit sha's
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)(we will only investigate if the tests are passing)