Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #7381

Closed
Open
Created Jul 27, 2014 by Administrator@rootOwner

[500] New branch form does not validate inputs and raises 500.

Created by: cirosantilli

Go to :project_id/branches/new.

Fill in with either an invalid:

  • Git branch name like one containing a space: a b
  • inexistent base branch like adsfqwerasdfqwer

Outcome: 500, the branch is simply not created, nil is returned, then something does nil.attribute and raises.

Expected outcome: controller validates, and shows the form again.

What GitHub does with spaces: automatically replaces them with hyphens. For other errors like pathname containing slashes it says: "Sorry, that branch name is invalid."

What is a valid new reference is described at: https://www.kernel.org/pub/software/scm/git/docs/git-check-ref-format.html and can be checked automatically with git check-ref-format. I don't think we should take a subset of it as that would still allow users to push such branches from the command line: let's just call git check-ref-format itself.

The same will happen when https://github.com/gitlabhq/gitlabhq/pull/7266 is done, which is why I found this in the first place.

Another validation problem: if the new branch name is already taken, the following happens: http://feedback.gitlab.com/forums/176466-general/suggestions/6201425-validate-branch-name-uniqueness-on-web-ui-creation . That should also be validated.

Assignee
Assign to
Time tracking