I just published a blog post about CRs Workflows, a new open source tool for managing code review comments embedded in source code, with reusable GitHub Actions workflows. If you’re interested in trying it out or sharing feedback, you can read more here: Launching CRs Workflows | CRs.
Thank you!
Here’s my feedback.
I read the post which as far as I can tell is just meta chatter about a release (uninteresting to me).
Then I clicked on the link mentioned in “Huh? What’s a CR?”. After reading that page I could get an idea of what a CR could be but I still didn’t know why I should care. I then tried to click on ‘Explanation’, but it seems that “This part of the documentation is currently empty.” as is most of the rest of the website.
Show me why I should care and why it’s better than sliced bread.
Sounds like a plausible instance of curse of knowledge on my part! Thanks for the feedback, and for sharing that stack trace, that’s very useful to me. Tacked as Address feedback #1 from discuss post · Issue #69 · mbarbin/crs · GitHub.
Thanks for reading.