Pascal Berger
Pascal Berger
An addin which adds support for writing diagrams would be nice (e.g. by using [mermaid](https://mermaidjs.github.io/))
It would be nice to have support for Cake Frosting projects for the task runner, templates and snippets
It would be nice to have the option to have build breaking if certain conditions for issues are met (e.g. issues exist, or issues of a certain severity exist)
Don't know exactly where the issue lies (in my repo, Cake.Recipe or JetBrains tools). If I use DupFinder or InspectCode in a GitHub Actions workflow with Cake.Recipe 2.0.0-alpha0493 (or 1.1.2)...
With support for Azure Pipelines comes the ability to have multiple jobs in a build, which e.g. run on different platform. This means that e.g. artifacts are created and published...
Cake.Issues.Recipe already contains a [build server abstraction layer](https://github.com/cake-contrib/Cake.Issues.Recipe/tree/develop/Cake.Issues.Recipe/Content/tasks/buildservers), which is available on the [IssuesData class](https://github.com/cake-contrib/Cake.Issues.Recipe/blob/develop/Cake.Issues.Recipe/Content/data/IssuesData.cake#L27). It should be possible to make the buildserver abstraction extensible, so that common functionality and...
Azure DevOps supports code coverage metrics (see [Code coverage metrics and branch policy for pull requests](https://docs.microsoft.com/en-us/azure/devops/server/release-notes/azuredevops2020?view=azure-devops&branch=releasenotes%2FAzureDevOpsServer2020#code-coverage-metrics-and-branch-policy-for-pull-requests)). It would be great if Cake.Recipe would automatically send coverage data while running under...
When running in Azure Pipelines test results should be reported to the build. Similar to #529 but for test results instead of coverage data.
We can add linting for markdown files using Cake.Markdownlint and output the issues using Cake.Issues.Markdownlint.