Mattias Granlund
Mattias Granlund
In #4438 I made it so locked hunks/files can only by amended into the commit they depend on, in response to #4423.
Sorry about the delay, just landed a fix.
We've landed some changes recently that take us one step further in #4315. Next we'll need to add support for multiple oauth flows in the backend, so stay tuned. We'll...
Is this pr still relevant?
Hey, sorry for leaving this PR without a follow-up. @krlvi @Byron what do we want to do here? I just tested this with `touch oh_no$'\n'.txt` and can confirm it breaks...
Feel free to re-open this issue if something comes up! Closing for now as it has been addressed in the recent commit list improvements. 🙏
The lack of a commit range feels like it makes Buildkite a non-starter for monorepo projects. > .. when git diff --name-only $COMMIT_RANGE would totally do the trick. Exactly this
>Basically we need a TS version of the rust structs for these objects Have you considered generating them? https://github.com/oscartbeaumont/tauri-specta
I was able to reproduce this, and it has to do with a flaw in our hunk locking/dependency calculation. Under some circumstances where a hunk _should_ be locked it shown...
This issue is now fixed in release 0.13.8, please re-open if the problem re-appears!