{"action":"created","issue":{"url":"https://api.github.com/repos/datalad/datalad/issues/1500","repository_url":"https://api.github.com/repos/datalad/datalad","labels_url":"https://api.github.com/repos/datalad/datalad/issues/1500/labels{/name}","comments_url":"https://api.github.com/repos/datalad/datalad/issues/1500/comments","events_url":"https://api.github.com/repos/datalad/datalad/issues/1500/events","html_url":"https://github.com/datalad/datalad/pull/1500","id":226843959,"number":1500,"title":"New `siblings` command","user":{"login":"mih","id":136479,"avatar_url":"https://avatars2.githubusercontent.com/u/136479?v=3","gravatar_id":"","url":"https://api.github.com/users/mih","html_url":"https://github.com/mih","followers_url":"https://api.github.com/users/mih/followers","following_url":"https://api.github.com/users/mih/following{/other_user}","gists_url":"https://api.github.com/users/mih/gists{/gist_id}","starred_url":"https://api.github.com/users/mih/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mih/subscriptions","organizations_url":"https://api.github.com/users/mih/orgs","repos_url":"https://api.github.com/users/mih/repos","events_url":"https://api.github.com/users/mih/events{/privacy}","received_events_url":"https://api.github.com/users/mih/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2017-05-07T09:38:01Z","updated_at":"2017-05-12T09:35:46Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/datalad/datalad/pulls/1500","html_url":"https://github.com/datalad/datalad/pull/1500","diff_url":"https://github.com/datalad/datalad/pull/1500.diff","patch_url":"https://github.com/datalad/datalad/pull/1500.patch"},"body":"Naming is analog to the `subdatasets` command that we already have. The purpose of this new command is to concentrate all code for sibling registration and meta data manipulation of siblings into a single command (set/change name, description, wanted policies, ....). Moreover, I would propose to treat \"here\" as another sibling and have the very same command also manipulate a standalone dataset.\r\n\r\nIn essence, all this command does are actions bound to a single dataset, plus a for-each-style recursive iteration of a dataset tree. For the latter we need to support a templating mechanism to e.g. transform a base URL to match a particular subdataset (so nothing new or fancy).\r\n\r\nList of related, unaddressed issues and previous discussions -- not necessarily TODO items for this PR, but the changes here should make those simpler to implement:\r\n\r\n- [ ] rewrite description #1484 \r\n- [ ] sibling/dataset configuration via templates #1462 \r\n- [ ] wanted policy setup #925 (related #921)\r\n- [ ] registration via datalad RIs #1438 \r\n- [ ] annex-only sibling tracking/update #1363\r\n- [ ] figure out if we want to treat \"here\" as yet another sibling and have the very same command also manipulate a standalone dataset (e.g. for description, wanted, ....). If so, how to indicate this best? `--name` no name could be `here`, but the we would need something for \"give me all info about all remotes\".\r\n- [ ] check (maybe via coverage) which parts of the legacy `add_sibling` became obsolete and gut the code accordingly\r\n- [ ] insufficient documentation #1017 \r\n\r\nActual TODOs:\r\n\r\n- [x] generalize `add_sibling` to `siblings` command #1235 - [ ] \r\n- [x] `siblings` is new-style generator\r\n- [x] `siblings` can remove a sibling (`remote remove`) #1483\r\n- [x] all internal use of `add_sibling` is via `siblings`\r\n- [ ] tests for `siblings remove`\r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/datalad/datalad/issues/comments/301031223","html_url":"https://github.com/datalad/datalad/pull/1500#issuecomment-301031223","issue_url":"https://api.github.com/repos/datalad/datalad/issues/1500","id":301031223,"user":{"login":"mih","id":136479,"avatar_url":"https://avatars2.githubusercontent.com/u/136479?v=3","gravatar_id":"","url":"https://api.github.com/users/mih","html_url":"https://github.com/mih","followers_url":"https://api.github.com/users/mih/followers","following_url":"https://api.github.com/users/mih/following{/other_user}","gists_url":"https://api.github.com/users/mih/gists{/gist_id}","starred_url":"https://api.github.com/users/mih/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mih/subscriptions","organizations_url":"https://api.github.com/users/mih/orgs","repos_url":"https://api.github.com/users/mih/repos","events_url":"https://api.github.com/users/mih/events{/privacy}","received_events_url":"https://api.github.com/users/mih/received_events","type":"User","site_admin":false},"created_at":"2017-05-12T09:35:46Z","updated_at":"2017-05-12T09:35:46Z","body":"Failing test is the general locking issue #1503"}}
{"actor":{"display_login":"mih"}}