{"action":"created","issue":{"url":"https://api.github.com/repos/laravel/internals/issues/196","repository_url":"https://api.github.com/repos/laravel/internals","labels_url":"https://api.github.com/repos/laravel/internals/issues/196/labels{/name}","comments_url":"https://api.github.com/repos/laravel/internals/issues/196/comments","events_url":"https://api.github.com/repos/laravel/internals/issues/196/events","html_url":"https://github.com/laravel/internals/issues/196","id":176122293,"number":196,"title":"[Proposal] Dry-run support for artisan schedule:run","user":{"login":"thejettdurham","id":5248042,"avatar_url":"https://avatars.githubusercontent.com/u/5248042?v=3","gravatar_id":"","url":"https://api.github.com/users/thejettdurham","html_url":"https://github.com/thejettdurham","followers_url":"https://api.github.com/users/thejettdurham/followers","following_url":"https://api.github.com/users/thejettdurham/following{/other_user}","gists_url":"https://api.github.com/users/thejettdurham/gists{/gist_id}","starred_url":"https://api.github.com/users/thejettdurham/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thejettdurham/subscriptions","organizations_url":"https://api.github.com/users/thejettdurham/orgs","repos_url":"https://api.github.com/users/thejettdurham/repos","events_url":"https://api.github.com/users/thejettdurham/events{/privacy}","received_events_url":"https://api.github.com/users/thejettdurham/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-09-09T22:05:51Z","updated_at":"2016-09-09T23:17:02Z","closed_at":null,"body":"I'm working on a project now with a fairly complex schedule logic for many long-running tasks in the Console Kernel. In this case, it would be helpful to have a way to simply validate the scheduling logic without actually kicking off any of the tasks.\r\n\r\nAdding an option to `artisan schedule:run` seems to be the most straight-forward approach. For example: `artisan schedule:run --dry` would list the commands that *would* run according to the schedule, but wouldn't actually run the command(s).\r\n\r\nIf there are no objections to this proposal and/or my suggested approach, I already have a PR ready for submission :)"},"comment":{"url":"https://api.github.com/repos/laravel/internals/issues/comments/246066367","html_url":"https://github.com/laravel/internals/issues/196#issuecomment-246066367","issue_url":"https://api.github.com/repos/laravel/internals/issues/196","id":246066367,"user":{"login":"tomschlick","id":70184,"avatar_url":"https://avatars.githubusercontent.com/u/70184?v=3","gravatar_id":"","url":"https://api.github.com/users/tomschlick","html_url":"https://github.com/tomschlick","followers_url":"https://api.github.com/users/tomschlick/followers","following_url":"https://api.github.com/users/tomschlick/following{/other_user}","gists_url":"https://api.github.com/users/tomschlick/gists{/gist_id}","starred_url":"https://api.github.com/users/tomschlick/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tomschlick/subscriptions","organizations_url":"https://api.github.com/users/tomschlick/orgs","repos_url":"https://api.github.com/users/tomschlick/repos","events_url":"https://api.github.com/users/tomschlick/events{/privacy}","received_events_url":"https://api.github.com/users/tomschlick/received_events","type":"User","site_admin":false},"created_at":"2016-09-09T23:17:02Z","updated_at":"2016-09-09T23:17:02Z","body":"Looks like a good submission to me.\r\n\r\nJust curious, how often do you see yourself needing to dry run things? Is it just for testing / debugging or is there some use case I'm not considering?"}}
{"actor":{"display_login":"tomschlick"}}