-
Notifications
You must be signed in to change notification settings - Fork 4
Further development of Cake.Issues.PullRequests.GitHub #4
Comments
@vhatsura Thanks for you interest in Cake.Issues. I definitely would like to see an integration with GitHub. The issue with public builds is that it is not so easy to implement in a secure way. There were some discussions with the Build Cross Check app if this can be used to write the issues here: justaprogrammer/BuildCrossCheck#90 |
Hi, @pascalberger. It's good news. I'll wait for release. |
is this usable already? |
@bonesoul Not yet, I plan to implement BCC Submission tool (#5), which would require you to have the tool installed, or install during build from Chooclatey (there's justaprogrammer/BCC-Submission#9 upstream for provding a library which can directly be used), and then writes the issues to GitHub checks. But with the current implementation of BCC Submission tool, this won't work for PR builds on a secure way (there's justaprogrammer/BuildCrossCheck#147 upstream to improve this) |
okay thanks for the reply. |
@vhatsura @bonesoul Cake.Issues.Recipe now supports reporting issues to GitHub when running on GitHub Action. See https://cakeissues.net/news/cake-issues-recipe-v0.4.2-released for details. Next step will be to move the corresponding code into this addin (see #79) |
Cake.Issues.PullRequests.GitHubActions has now been released. See https://cakeissues.net/docs/pull-request-systems/github-actions/ for documentation. |
Hi, @pascalberger.
First of all, big thanks for your work under Cake.Issues and all related stuff. It's awesome extension for build process with rich capabilities.
So, what I want to ask you? Do you plan further development of
Cake.Issues.PullRequests.GitHub
? It should be useful at least for Cake community.From my side I can offer help in development. but I need understand what should be done and in what order.
The text was updated successfully, but these errors were encountered: