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

Closed
Open
Created Jan 30, 2012 by Administrator@rootOwner

Time(wrong timezone and time usage)

Created by: funkycode

the tree and commits showen and sorted by the client side changes: for example if my clock is wrong and is +15 minutes( or i don't use timezone but UTC) and i pulled commit, than if person with right time or time than is lower than mine makes the commit after me in this gap of 15 mins would lead to gitlab showing only my commits would be shown, while git repo would be still updated.

I think the time calculation of when the pull was performed or any changes should be made localy, using the server side time.

Assignee
Assign to
Time tracking