{"action":"closed","issue":{"url":"https://api.github.com/repos/git-lfs/git-lfs/issues/3380","repository_url":"https://api.github.com/repos/git-lfs/git-lfs","labels_url":"https://api.github.com/repos/git-lfs/git-lfs/issues/3380/labels{/name}","comments_url":"https://api.github.com/repos/git-lfs/git-lfs/issues/3380/comments","events_url":"https://api.github.com/repos/git-lfs/git-lfs/issues/3380/events","html_url":"https://github.com/git-lfs/git-lfs/issues/3380","id":380496578,"node_id":"MDU6SXNzdWUzODA0OTY1Nzg=","number":3380,"title":"Q: git status vs git lfs status","user":{"login":"dashesy","id":873905,"node_id":"MDQ6VXNlcjg3MzkwNQ==","avatar_url":"https://avatars2.githubusercontent.com/u/873905?v=4","gravatar_id":"","url":"https://api.github.com/users/dashesy","html_url":"https://github.com/dashesy","followers_url":"https://api.github.com/users/dashesy/followers","following_url":"https://api.github.com/users/dashesy/following{/other_user}","gists_url":"https://api.github.com/users/dashesy/gists{/gist_id}","starred_url":"https://api.github.com/users/dashesy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dashesy/subscriptions","organizations_url":"https://api.github.com/users/dashesy/orgs","repos_url":"https://api.github.com/users/dashesy/repos","events_url":"https://api.github.com/users/dashesy/events{/privacy}","received_events_url":"https://api.github.com/users/dashesy/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-11-14T01:28:38Z","updated_at":"2018-11-14T16:57:39Z","closed_at":"2018-11-14T16:57:39Z","author_association":"NONE","body":"Is there any design rationale to keep both `git status` and `git lfs status`? could they be combined so that `git status` would know about lfs updates as well?\r\n\r\nThat would clear a lot of confusions about which files are lfs and which ones are not.\r\n\r\nFor example right now `git lfs status` outputs:\r\n\r\n    Git LFS objects to be committed:\r\n\r\nbut then displays files that are not really \"Git LFS objects\" to be committed (only some are) and `git status` has no idea about lfs objects"}}
{"actor":{"display_login":"bk2204"}}