Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 2
    • Merge requests 2
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Merge requests
  • !14428

Resolve "Cannot rename a hashed project"

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Douglas Barbosa Alexandre requested to merge 38202-cannot-rename-a-hashed-project into master Sep 21, 2017
  • Overview 18
  • Commits 3
  • Pipelines 14
  • Changes 4

What does this MR do?

Does not check if an invariant hashed storage path exists on disk when renaming projects.

Are there points in the code the reviewer needs to double check?

No.

Why was this MR needed?

Users can't rename projects created after the hashed storage was enabled.

Does this MR meet the acceptance criteria?

  • Changelog entry added, if necessary
  • Documentation created/updated
  • API support added
  • Tests added for this feature/bug
  • Review
    • Has been reviewed by UX
    • Has been reviewed by Frontend
    • Has been reviewed by Backend
    • Has been reviewed by Database
  • Conform by the merge request performance guides
  • Conform by the style guides
  • Squashed related commits together

What are the relevant issue numbers?

Closes #38202 (closed)

Edited Oct 03, 2017 by Nick Thomas
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: 38202-cannot-rename-a-hashed-project