Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't Require knope.toml for basic release workflow #255

Closed
dbanty opened this issue Aug 27, 2022 · 0 comments · Fixed by #286
Closed

Don't Require knope.toml for basic release workflow #255

dbanty opened this issue Aug 27, 2022 · 0 comments · Fixed by #286
Labels
🎸 Feature New feature or request

Comments

@dbanty
Copy link
Member

dbanty commented Aug 27, 2022

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).

@dbanty dbanty added the 🎸 Feature New feature or request label Aug 27, 2022
dbanty added a commit that referenced this issue Sep 25, 2022
… `--generate`) with no `knope.toml` file.

Closes: #255
dbanty added a commit that referenced this issue Sep 25, 2022
…`--generate`) with no `knope.toml` file. (#286)

Closes: #255

Co-authored-by: Dylan Anthony <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🎸 Feature New feature or request
Projects
None yet
1 participant