{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/web-platform-tests/issues/4990","repository_url":"https://api.github.com/repos/w3c/web-platform-tests","labels_url":"https://api.github.com/repos/w3c/web-platform-tests/issues/4990/labels{/name}","comments_url":"https://api.github.com/repos/w3c/web-platform-tests/issues/4990/comments","events_url":"https://api.github.com/repos/w3c/web-platform-tests/issues/4990/events","html_url":"https://github.com/w3c/web-platform-tests/issues/4990","id":209620564,"number":4990,"title":"Add a \"don't ping reviewers\" sigil","user":{"login":"domenic","id":617481,"avatar_url":"https://avatars.githubusercontent.com/u/617481?v=3","gravatar_id":"","url":"https://api.github.com/users/domenic","html_url":"https://github.com/domenic","followers_url":"https://api.github.com/users/domenic/followers","following_url":"https://api.github.com/users/domenic/following{/other_user}","gists_url":"https://api.github.com/users/domenic/gists{/gist_id}","starred_url":"https://api.github.com/users/domenic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/domenic/subscriptions","organizations_url":"https://api.github.com/users/domenic/orgs","repos_url":"https://api.github.com/users/domenic/repos","events_url":"https://api.github.com/users/domenic/events{/privacy}","received_events_url":"https://api.github.com/users/domenic/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":17,"created_at":"2017-02-22T23:56:20Z","updated_at":"2017-02-24T16:05:38Z","closed_at":null,"body":"Us poor URL reviewers get a lot of pings from bots asking us to review cases when the WPT infra folks are actually just using URL files as a testing ground for infra changes.\r\n\r\nIt would be ideal if this didn't happen. One way of doing that would be, e.g., for the bots to not ping if the PR title contains \"[infra]\" or similar."},"comment":{"url":"https://api.github.com/repos/w3c/web-platform-tests/issues/comments/282329466","html_url":"https://github.com/w3c/web-platform-tests/issues/4990#issuecomment-282329466","issue_url":"https://api.github.com/repos/w3c/web-platform-tests/issues/4990","id":282329466,"user":{"login":"jugglinmike","id":677252,"avatar_url":"https://avatars.githubusercontent.com/u/677252?v=3","gravatar_id":"","url":"https://api.github.com/users/jugglinmike","html_url":"https://github.com/jugglinmike","followers_url":"https://api.github.com/users/jugglinmike/followers","following_url":"https://api.github.com/users/jugglinmike/following{/other_user}","gists_url":"https://api.github.com/users/jugglinmike/gists{/gist_id}","starred_url":"https://api.github.com/users/jugglinmike/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jugglinmike/subscriptions","organizations_url":"https://api.github.com/users/jugglinmike/orgs","repos_url":"https://api.github.com/users/jugglinmike/repos","events_url":"https://api.github.com/users/jugglinmike/events{/privacy}","received_events_url":"https://api.github.com/users/jugglinmike/received_events","type":"User","site_admin":false},"created_at":"2017-02-24T16:05:38Z","updated_at":"2017-02-24T16:05:38Z","body":"After sleeping on this, I think it's possible that I may have been suffering\r\nfrom functional fixedness. Whatever the patch's origin, the use case is: \"I want\r\nto validate this change in CI without notifying any AUTHORS in a pull request.\"\r\nTravisCI is currently configured to \"build branches,\" meaning that simply\r\npushing to a branch in the upstream repository triggers a build--no pull request\r\nnecessary. So whether you are testing infrastructure changes or validating a\r\ndownstream patch to test files, you can already enjoy the benefit of CI results\r\nwithout creating spam for others: just create a branch with your work in the\r\nupstream repository.\r\n\r\nThis practice would not only avoid additional complexity in the infrastructure\r\ncode, it would also limit the amount of domain-specific details that\r\ncontributors have to discover/learn/memorize. Admittedly, it doesn't address\r\ntwo scenarios supported by the proposed \"label\"/\"sigil\" feature:\r\n\r\n1. \"I want to validate a patch that specifically concerns the logic for posting\r\n   a comment to GitHub.\"\r\n2. \"I want to 'pre-validate' my patch, but I do not have the necessary\r\n   permissions to create a branch in the upstream repository.\"\r\n\r\nI think `1` is probably rare enough to forget about. I'm not sure `2` is\r\nactually valid since the \"pre-validation\" use case has only been requested by\r\ndownstream consumers that already have merge rights.\r\n\r\nWhat do folks here think?"}}
{"actor":{"display_login":"jugglinmike"}}