Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • D dbscripts
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Arch Linux
  • dbscripts
  • Merge requests
  • !29

db-move: Clarify error message when the specified repo isn't correct for the...

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Johannes Löthberg requested to merge demize/dbscripts:db-move-better-invalid-repo-error into master Oct 27, 2021
  • Overview 0
  • Commits 1
  • Pipelines 1
  • Changes 2

db-move: Clarify error message when the specified repo isn't correct for the current dbscripts instance

It's not entirely clear what a "configured repository" is, but hopefully saying that the given repo isn't a "valid repository" is clearer.

In typical use this will result in an error like this:

==> ERROR: extra is not a valid repository for /community/db-move

or this:

==> ERROR: community-testing is not a valid repository for /packages/db-move
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: db-move-better-invalid-repo-error