One of the premises that leaded to this toolkit being born was that changes on non user-facing parts of a repository, such as build system, should not result in a new user-facing release.
However, as of now dependency bumps of github actions will result in a new release. An easy way to prevent this is to add the .github to excluded-dirs in generate-yaml.
Doing this by default is very tricky, so allegedly the best way to do so is to put it on every example we write.
One of the premises that leaded to this toolkit being born was that changes on non user-facing parts of a repository, such as build system, should not result in a new user-facing release.
However, as of now dependency bumps of github actions will result in a new release. An easy way to prevent this is to add the
.githubtoexcluded-dirsingenerate-yaml.Doing this by default is very tricky, so allegedly the best way to do so is to put it on every example we write.