In #97, the idea of making a connection between GitHub issue and Pharo is raised.
I have a class that does that.
It reads all issues in an GitHub issue list for a given repository. Microdown is default, but it can be changed
My reason for wanting it was because I needed something I can see inside Pharo.
At the moment, one can write this in Playground:
Microdown asRichText: (AIAGitHub default llmOpenIssue: 97 ).
And it returns a Microdown text like this:
If it is useful, I need an other name for the class, and where to put it (which Microdown package area)
In #97, the idea of making a connection between GitHub issue and Pharo is raised.
I have a class that does that.
It reads all issues in an GitHub issue list for a given repository. Microdown is default, but it can be changed
My reason for wanting it was because I needed something I can see inside Pharo.
At the moment, one can write this in Playground:
And it returns a Microdown text like this:
If it is useful, I need an other name for the class, and where to put it (which Microdown package area)