Pascal Berger

Cake.Markdownlint uses [markdownlint-cli](https://github.com/igorshubovych/markdownlint-cli) which requires node to be installed. Not sure how we can handle this the best. Maybe we can check and run the linting if the tool is...

There are three things to do here: 1. Run markdownlint as part of Cake.Recipe 2. Support markdownlint input in Cake.Issues.Recipe (https://github.com/cake-contrib/Cake.Issues.Recipe/issues/5 / https://github.com/cake-contrib/Cake.Issues.Recipe/issues/6) 3. Pass markdownlint log to Cake.Issues.Recipe If...

I can add the support in Cake.Issues.Recipe very quick, since issue provider already exists and reporting capabilities come for free. The reason it is not in there yet, is not...

Support for markdownlint has been released in [Cake.Issues.Recipe 0.3.4](https://github.com/cake-contrib/Cake.Issues.Recipe/releases/tag/0.3.4)

Yes, I can look at it (but some other issues which I need to tackle first)

> @pascalberger is this now a feature of Cake.Issues.Recipe? Not yet, but it should be implemented there. I created https://github.com/cake-contrib/Cake.Issues.Recipe/issues/126 for tracking it. For me it would be OK to...

Another possibility would be to switch builds for pull requests to Azure Pipelines which would bring parallel builds

Cake.Issues.Recipe has solved this with a [BuildIdentifier](https://cakeissues.net/docs/recipe/configuration#general) parameter, which can be set in the build script to define a different value for different runs.

Cake.Recipe should set `IssuesParameters.BuildIdentifier` for proper Cake.Issues.Recipe configuration

@gep13 For Cake.Issues.Recipe integration tests it is set here: https://github.com/cake-contrib/Cake.Issues.Recipe/blob/798396d6931c20f58d631c0b7529ab00ed82338c/tests/integration/build.cake#L34 This results in the following artifacts: https://dev.azure.com/cake-contrib/Cake.Issues.Recipe/_build/results?buildId=4930&view=artifacts&type=publishedArtifacts