You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To make adoption even easier, it would be a good idea to allow someone to run basic workflows (notably knope release for starters) without any configured knope.toml. This will inspect the project the same way knope --generate does to determine the best guess for a release workflow, then run it.
It may be worth making some of the output more verbose so people can see what knope thinks is the right thing—particularly with knope release --dry-run.
Further, if a project does have a knope.toml but does not declare any of the built-in workflows—the built-in flows can still be called (a la cargo-make).
The text was updated successfully, but these errors were encountered:
To make adoption even easier, it would be a good idea to allow someone to run basic workflows (notably
knope release
for starters) without any configuredknope.toml
. This will inspect the project the same wayknope --generate
does to determine the best guess for arelease
workflow, then run it.It may be worth making some of the output more verbose so people can see what
knope
thinks is the right thing—particularly withknope release --dry-run
.Further, if a project does have a
knope.toml
but does not declare any of the built-in workflows—the built-in flows can still be called (a lacargo-make
).The text was updated successfully, but these errors were encountered: