cranko icon indicating copy to clipboard operation
cranko copied to clipboard

Turn the release crank.

Results 10 cranko issues
Sort by recently updated
recently updated
newest added

Thank you for the great project. I really like the idea of just-in-time versioning in monorepos. Would you consider supporting [Pijul](https://pijul.com/)? It's a new version control system based on patches....

Hi, i just played around with your project to see if it might help deploying a monorepo but it seems the you tools ignores the `[patch.crates-io]` block

I want to use Github CI but I don’t know how to configure it. Can you create a template project?

I was reading through the manual and came upon this in section 4.1: > NOTE: The goal is for Cranko to recognize all sorts of projects, but currently it only...

Right now these commits are just labeled "Release commit created by Cranko", etc. If there's one package we should include its name. If there are multiple, we do something sensible...

good first issue

We should document `major bump`, `minor bump`, etc. This should go into the Concepts section of the book.

Right now we only have the generic Markdown format. One day we'll probably need to support more options. This should go in the Concepts section of the book.

But how :-( Need a way to create lots of quickie repos with interesting histories across multiple branches.

Upon `apply-versions`, check: - That current origin `rc` tip is an ancestor of new `rc` tip - That current origin `release` main-dev commit is an ancestor of new `rc` main-dev...

Sometimes after doing a `cranko commit`, it turns out that there's a problem, or I forgot to stage a package, and I want to go back and edit the staging...