Skip to content

Resolve "Failure to create MR on staging"

Marc Shaw requested to merge 337787-failure-to-create-mr-on-staging into master

What does this MR do?

Kibana Logs: https://nonprod-log.gitlab.net/app/discover#/doc/ed942d00-5186-11ea-ad8a-f3610a492295/pubsub-rails-inf-gstg-000329?id=Rx53F3sBIGIRKJPsM0Qn

We are currently calling project.repository.new_commits from lib/gitlab/checks/changes_access.rb:43. This method call is going to be calling the app/model/repository new_commits method, rather than the raw_repository.new_commits method. These two have different signatures, so we should make these two take the same arguments.

Screenshots or Screencasts (strongly suggested)

How to setup and validate locally (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Security

Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • Security reports checked/validated by a reviewer from the AppSec team

Related to #337787 (closed)

Edited by Marc Shaw

Merge request reports