{"comment":{"url":"https://api.github.com/repos/macgitver/libGitWrap/comments/10339878","html_url":"https://github.com/macgitver/libGitWrap/commit/7960495a20006adecc10009c4f5c1dcf9ccda06d#commitcomment-10339878","id":10339878,"user":{"login":"antis81","id":440517,"avatar_url":"https://avatars.githubusercontent.com/u/440517?v=3","gravatar_id":"","url":"https://api.github.com/users/antis81","html_url":"https://github.com/antis81","followers_url":"https://api.github.com/users/antis81/followers","following_url":"https://api.github.com/users/antis81/following{/other_user}","gists_url":"https://api.github.com/users/antis81/gists{/gist_id}","starred_url":"https://api.github.com/users/antis81/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/antis81/subscriptions","organizations_url":"https://api.github.com/users/antis81/orgs","repos_url":"https://api.github.com/users/antis81/repos","events_url":"https://api.github.com/users/antis81/events{/privacy}","received_events_url":"https://api.github.com/users/antis81/received_events","type":"User","site_admin":false},"position":null,"line":null,"path":"","commit_id":"7960495a20006adecc10009c4f5c1dcf9ccda06d","created_at":"2015-03-23T09:08:15Z","updated_at":"2015-03-23T09:08:15Z","body":"Damn, actually my first thought was to open a PR for this, but then I thought, this is a very small change and already correct. These are my first steps with the \"private branch workflow\" though. \r\n\r\nAah yes, I completely forgot about the \"worktree\" term. I think I'll write to the libgit2 folks about it to rename that stuff consistently into either \"worktree\" or \"work_tree\" to use the Git term consistently then (or write a small PR). Actually at my former workplace we used a mechanism to auto-check agree'd terms throughout the product (i.e. several millions lines of code - really powerful stuff).\r\n\r\nTo make it short:\r\nI think you'll also agree to \"workTreePath\" then.\r\n\r\nWhen ready, it reads like:\r\n* Repository::path();\r\n  Returns the full absolute path to the very git repository (bare or non-bare) itself (either \".git\" folder or \"linked folder\" from the \".git\" file -> (docs will be corrected as well :smile:)\r\n* Repository::workTreePath();\r\n  Returns the absolute path to the worktree. (empty for bare repositories, as they don't have a worktree)\r\n\r\nLet me add an rough idea for future improvements to MGV v0.1:\r\nYou're right. A submodule only exists (and has a worktree), if the parent repository is checked out (non-bare). We have the \".gitmodules\" file sleeping in the commits, which acutally carries the information, which submodules are linked. If this file exists, we can actually provide the information, that a) the repo links submodules and optionally b) a preview of those nasty url's. This information has to be gathered from the commits though and that's why I think we should do it in a future version. I'll write a feature request for MGV v0.2 in redmine, to not forget about it."}}