Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
bitmask-dev
bitmask-dev
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 282
    • Issues 282
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • leap
  • bitmask-devbitmask-dev
  • Issues
  • #8939

Closed
Open
Opened Jun 15, 2017 by meskio@meskio⛺Owner

rename export --fetch to something more meaningfull in the API

It's weird to call export to fetch keys remotely. Can we have a more meaningful naming in the API?

Assignee
Assign to
Next
Milestone
Next (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: leap/bitmask-dev#8939