Aleksander Heintz
Aleksander Heintz
Feel free to just take the code from my aligned buffer crates.
I just thought I'd chime in here, cause I just ran into an issue where I would like to be able to map "place in code" to something else. Basically,...
I don't like checking the commit message (as that can be a bit brittle). The committer would probably work though. That being said, having to "work around" this is a...
I'm assuming `release-plz` knows if it's running in a release commit? If not, that's the first part I would add support for. Then it would simply be something like `only_publish_in_release_commits`...
I'm used to `release-please` where I'm able to take actions (like publishing crates) if and only if a new release was just created (ie, it's running on the release commit)....
With PRs you have a lot more data to work with. You could specify a tag for instance - or the PR author (which is not necesarily the same as...
I also feel the release-please workflow is much better. The process there is like this: 1. I push to (or merge to) main 2. Release-please runs and creates/updates a PR...
I don't run cargo publish by myself. It happens in the same github action that runs release-please. But sure, the semver violation checks are definitely one of the reasons I'm...
How about checking the prototype? If it's a `Function` object, then it's a function. If it's a sub-type of `Function`, then it's a class (most likely)?
Oh, wait. I'm completely thinking wrongly about this. My bad.