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

Closed
Open
Created Mar 22, 2014 by Administrator@rootOwner

Merge Request email subjects

Created by: rspeicher

So revision 3d7194f0 introduced, among other things, this method, which appears to override the subject method of Notify. That's fine, except that it doesn't. It never even gets called. This might have been noticed sooner if there had been any tests for it.

On top of not actually working, the thing it's trying to do isn't done very well. Why re-create the entire subject method when we could just unshift the new information onto the extras var and call super? Why do we sometimes use @merge_request and other times just use merge_request, seemingly at random?

Should I try fixing it? Do we want to just remove it since no one's seemed to miss it so far?

ping @karlhungus

Assignee
Assign to
Time tracking