Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • thg thg
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 846
    • Issues 846
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

In order to prepare the next update of Heptapod based on Gitlab 16.0. The instance will be unavailable on 2023-10-06 between 19:00 and 23:00 UTC+2

  • mercurialmercurial
  • TortoiseHgTortoiseHg
  • thgthg
  • Issues
  • #5577
Closed
Open
Issue created Jul 18, 2020 by php4fan@php4fan

selects last commit instead of working directory by default when opening a repository

Steps to reproduce:

  • lauch thg
  • double click on a repository in the list in the left panel to open it

Expected behavior:

  • the working directory should be selected, and the changes in it (if any) listed by default. Then you can go browse any of the commits if you want. But the status of the working directory should be the first thing you see upon opening a repository. Used to be this way

Observed behavior:

  • the last committed changeset is selected by default and initially shown instead.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking