Skip to content

ProjectMergeRequest.commits() has surprising returns #266

@AstraLuma

Description

@AstraLuma

I'm not sure why exactly, but it seems that .commits() (v4) has three kinds of returns:

  • An actual list of ProjectCommit objects
  • An empty list (even though the merge request has commits attached to it)
  • Raising a 404 error

I'm finding this very puzzling, especially since the endpoint is not documented to return a 404.

(This is all on the same project, btw.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions