Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.cmdline beat.cmdline
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 22
    • Issues 22
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.cmdlinebeat.cmdline
  • Issues
  • #68
Closed
Open
Issue created May 15, 2020 by Amir MOHAMMADI@amohammadiMaintainer

beat exp fork command is cumbersome to use

When you fork an experiment in the command line, you have to something like:

$ beat exp fork test/test/iris/1/iris amir/test/iris/1/means

but you can only change the username and name of the experiment when you fork.

When using beat.editor 2.0.0, when I fork an experiment, it only asks for the exp name. Beat.editor somehow decided to put the forked experiment under user amir but I don't know yet how it decided on that.

Shouldn't this command be also similar? Something like:

$ beat exp fork test/test/iris/1/iris means
$ beat exp fork --user amir test/test/iris/1/iris means
Assignee
Assign to
Time tracking