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

Closed
Open
Created Sep 30, 2013 by Administrator@rootOwner

Force push bug

Created by: axos88

Hello!

Amending and push -f -ing a commit to the repo does not modify the references in the issues.

For ex. I push a commit with text 'closes #4 (closed)', and then amending it and pushing again (--force) will leave the "status changed to close by commit" pointing to the old commit, rather than the new one.

This may very well lead to problems during code review.

I know pushing --force should be avoided, however some developers are using it, and anyways it should not introduce orphan references in the gitlab repository either.

Assignee
Assign to
Time tracking