Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • vidjil vidjil
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,738
    • Issues 1,738
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 104
    • Merge requests 104
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • vidjilvidjil
  • vidjilvidjil
  • Issues
  • #2741
Closed
Open
Issue created Oct 20, 2017 by Mathieu Giraud@magiraudOwner

CLI: valeurs NO_LIMIT

Bloque #2732 (closed).

Plusieurs options utilisent atoi_NO_LIMITou atof_NO_LIMIT pour accepter la chaîne all. Pourrait-on faire un Option * qui se charge de cela, ou un autre mécanisme générique ?

Notons qu'on ne peut pas transformer la valeur en NO_LIMIT_VALUE en NO_LIMIT, car c'est après la conversion. On devra probablement toucher au callback.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking