For some reason, the debugger starts working in the created projects when we remove these lines:

[tool:pytest]
addopts = --cov=project/

Currently scaraplate rollup doesn't have a no-action mode, i.e. it always writes the changes. It might be useful to add a no-action mode, which just checks if there would be any changes made by rollup and prints diff and sets an exit code (0 -- success -- for no changes; and 1 -- error -- for any changes).

This mode can be used in CI pipelines to ensure that new changes didn't introduce any new

Summary

I would like some documentation about how I can test the template if I do changes and compile it at home.

Context

I would like to try to implement some changes that I would like to have

Your Environment

• Developer environment: Visual Studio 2017

Checklist

• I have read the CODE OF CONDUCT document.
• I have searched the issues_ list and could not