3 ms·
These are interactive checklists. You can add items by creating a comment: > @bugout-dev check require <item> and cross them off by creating a comment: > @bu
by zomglings 6y ago
These are interactive checklists. You can add items by creating a comment:
> @bugout-dev check require <item>
and cross them off by creating a comment:
> @bugout-dev check accept <item>
The cool thing about this is that you can even create GitHub Actions that require or accept checks since everything is command/comment based.
- verdverm 6y agoI can edit the markdown to add and remove lists. I don't see the need to add yet another app that can access my repos
- zomglings 6y agoThe reason markdown checklists are not appealing to me is that: 1. Only the comment creator or a repository maintainer can edit a markdown checklist created the way you suggest. You may want to open a checklist up to an entire team. 2. The markdown checklist doesn't block a PR the way that a check does. This is because a manual markdown checklist is not canonical for a pull request. The checklists here are canonical (at least for the Bugout app). This is important if merging the PR makes a production change. Please don't mistake me, not trying to push the app down your throat. I respect that this may not bring enough value to justify an app installation with access to your repos. Just want to explore your objections.
- verdverm 6y agoApp and subscription overload.
- deleted 6y ago[deleted]