Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Merge requests
  • !8224

Merged
Created Nov 01, 2014 by Administrator@rootOwner

Expose projects_limit through users API if UserFull.

  • Overview 10
  • Commits 1
  • Changes 3

Created by: liammonahan

If the authenticated user of the API is an admin, they will be using the Entities::UserFull set of exposed params. This patch exposes User.projects_limit and updates the relevant documentation and tests.

As background justification for this proposed change, I had a use case to want to see how many projects a user is limited to for our site's GitLab installation. We do space auditing as a multiplier of the projects limit.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: github/fork/liammonahan/master