René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Don't add trailing slash when reporting repository path or workdir","articleBody":"### Reproduction steps\r\n\r\nInvoke the [git_repository_path](https://libgit2.github.com/libgit2/#HEAD/group/repository/git_repository_path) or [git_repository_workdir](https://libgit2.github.com/libgit2/#HEAD/group/repository/git_repository_workdir). Observe that the directory path contains a trailing slash.\r\n\r\n### Expected vs Actual behavior\r\n\r\nIt's unconventional to add a trailing slash to the directory name returned by these methods. It also differs from the values reported by the native git client.\r\n\r\nCase in point.\r\n\r\nNative git:\r\n\r\n```\r\n$ git rev-parse --absolute-git-dir\r\n/home/user/projects/libgit2/.git\r\n```\r\n\r\nlibgit2\r\n\r\n```\r\ngit_repository_path(repo)\r\n//=\u003e /home/user/projects/libgit2/.git/\r\n```\r\n\r\nNative git:\r\n\r\n```\r\n$ git worktree list\r\n# /home/user/projects/libgit2    937e7e2 [master]\r\n```\r\n\r\nlibgit2\r\n\r\n```\r\ngit_repository_workdir(repo)\r\n//=\u003e /home/user/projects/libgit2/\r\n```\r\n\r\nI believe these values should either match the native git client or this difference should be highlighted in the documentation.\r\n\r\n### Version of libgit2 (release number or SHA1)\r\n\r\nvia nodegit 0.21.1 (libgit2 v0.26.0 according to the nodegit README at the time of that release)\r\n\r\n### Operating system(s) tested\r\n\r\nLinux, Windows, macOS","author":{"url":"https://github.com/mojavelinux","@type":"Person","name":"mojavelinux"},"datePublished":"2018-03-18T05:23:02.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/4583/libgit2/issues/4583"}