{"action":"opened","issue":{"url":"https://api.github.com/repos/psss/fmf/issues/43","repository_url":"https://api.github.com/repos/psss/fmf","labels_url":"https://api.github.com/repos/psss/fmf/issues/43/labels{/name}","comments_url":"https://api.github.com/repos/psss/fmf/issues/43/comments","events_url":"https://api.github.com/repos/psss/fmf/issues/43/events","html_url":"https://github.com/psss/fmf/issues/43","id":336247370,"node_id":"MDU6SXNzdWUzMzYyNDczNzA=","number":43,"title":"Ignore metadata subtrees","user":{"login":"psss","id":2803150,"node_id":"MDQ6VXNlcjI4MDMxNTA=","avatar_url":"https://avatars2.githubusercontent.com/u/2803150?v=4","gravatar_id":"","url":"https://api.github.com/users/psss","html_url":"https://github.com/psss","followers_url":"https://api.github.com/users/psss/followers","following_url":"https://api.github.com/users/psss/following{/other_user}","gists_url":"https://api.github.com/users/psss/gists{/gist_id}","starred_url":"https://api.github.com/users/psss/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/psss/subscriptions","organizations_url":"https://api.github.com/users/psss/orgs","repos_url":"https://api.github.com/users/psss/repos","events_url":"https://api.github.com/users/psss/events{/privacy}","received_events_url":"https://api.github.com/users/psss/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-06-27T14:10:40Z","updated_at":"2018-06-27T14:10:40Z","closed_at":null,"author_association":"OWNER","body":"When exploring directories `fmf` should probably ignore other metadata trees in the directory tree. Yesterday we've discussed the following real-life scenario which seems to support this approach:\r\n\r\nStandard Test Roles support fetching tests from remote repositories. At the same time there can be tests stored directly in dist-git. When these two options are mixed we should still be able to gather reasonable metadata for both.\r\n\r\nHere's a simple example directory structure:\r\n\r\n    .\r\n    ├── fetched\r\n    │   ├── fetched1\r\n    │   ├── fetched2\r\n    │   ├── fetched3\r\n    │   └── main.fmf\r\n    ├── main.fmf\r\n    ├── stored1\r\n    ├── stored2\r\n    └── stored3\r\n\r\nCurrent output in the main `tests` directory (note the modified node identifiers):\r\n\r\n    /stored1\r\n    /stored2\r\n    /stored3\r\n    /fetched/fetched1\r\n    /fetched/fetched3\r\n    /fetched/fetched2\r\n\r\nCurrent output for the fetched test cases in `tests/fetched`:\r\n\r\n    /fetched1\r\n    /fetched3\r\n    /fetched2\r\n\r\nExpected output for the main directory:\r\n\r\n    /stored1\r\n    /stored2\r\n    /stored3\r\n\r\nGuys, what are your thoughts on this?"}}
{"actor":{"display_login":"psss"}}