3 ms·
Why do you use labels and comments instead of GitHub’s Statuses API [1]? [1]: https://developer.github.com/v3/repos/statuses/#create-a-status https://developer
by hk__2 8y ago
Why do you use labels and comments instead of GitHub’s Statuses API [1]?
[1]: https://developer.github.com/v3/repos/statuses/#create-a-status https://developer.github.com/v3/repos/statuses/#create-a-sta...
- eat_veggies 8y ago> Warning: The API may change without advance notice during the preview period. Preview features are not supported for production use.
- WillAbides 8y ago“avatar_url” is the only part of that endpoint in preview, so that warning only applies to that field. I can see how the notification isn’t clear on that point, and I will bring that up.
- eat_veggies 8y agoI see. Thanks for the clarification!
- WillAbides 8y agoI’m not involved in this project, but I would guess that it’s because it validates both issues and PRs, but only PRs have statuses on GitHub, More precisely, only commits have statuses, and issues aren’t associated with commits.
- schachtecode 8y agoThis is exactly correct. I haven't finished the pull request feature yet, what you're seeing on the repo is just issues. I will be taking requests for any desired features
- schachtecode 8y agoHey there. I'm still coding this, but when I finish pull requests, it will have status checks. Comments are for issues