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
  • #1304

Closed
Open
Created Aug 26, 2012 by Administrator@rootOwner

Bug: repositories with dot in git path do not trigger hooks

Created by: Mikulas

Tested on: Gitlab 2.8.2, git 1.7.2.5

Creating a new gitlab repo myproject.com automatically replaces the dot with an underscore in both the project url and git path. There are however no edit limitations. I've changed the git path from proposed myproject_com back to myproject.com. No errors are shown when the project is created.

However, hooks are not triggered for such repository. The test hook button works fine.

For repositories with the very same setup and content but without the dot in git path hooks work as expected.

Assignee
Assign to
Time tracking