Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Rename repository

Open
#255 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github, php

Research direction

Start by reviewing the GitHub repository settings and the corresponding Packagist package metadata, including the canonical Composer name. Confirm the intended lowercase repository name, URL redirect behavior, and Packagist update; also determine whether the similarly named DoctrineModuleORMModule and DoctrineModuleMongo projects are in scope.

Written by the indexing model from the issue text.

Description

Enhancement

Hi @Ocramius ,

For homogeneity purpose with how composer name packages, I think it would be a good idea to rename the GitHub project from "DoctrineModule" to "doctrine-module". I tried it with my own projects, it's absolutely painless, it breaks nothing (even the old URL is redirected to the new one). It just provides more homogeneity and it seems like some projects like Doctrine adopte this (as well as zf itself).

(I'm not going to raise in issue but the same applies for DoctrineModuleORMModule, DoctrineModuleMongo...)

EDIT : in fact, the composer package canonical also needs to be updated on Packagist.

Dominant language
PHP
Stars
392
Forks
263
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from doctrine/DoctrineModule

All issues in doctrine/DoctrineModule

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.