extrawurst
extrawurst
once the commit popup is open there should be a `Amend` option. Is that what you had in mind?
ok instrumentation reveals that we spent 15% in `bevy_winit::system::create_monitors`:  The reason for this is because we detect a new *unseen* monitor each frame and spawn it: https://github.com/bevyengine/bevy/blob/75c92fb47b1d971134b8b96d83f1a054e1e87623/crates/bevy_winit/src/system.rs#L166 just to...
> I also imagine that there's a lot of cost to the info! log while it's spamming. Not that this is a "good" solution but compiling out that log may...
@madsmtm would be great to have your opinion
@mockersf your workaround can be swapped against proper monitor handle partialeq: https://github.com/rust-windowing/winit/releases/tag/v0.30.6
it looks like https://github.com/GitoxideLabs/gitoxide/pull/2102 is merged, so we can move forward on this, right?
> seems to be somewhat intentional [..] results in the committer being unchanged isnt that exactly the opposite of what the bug report states?
@ItsHarper > My understanding is that the committer should change, yeah But your bug report says: > Observe that you are now listed as the commit author So what is...
Oh interesting. Makes sense. the signed amend is a hack because there is no such thing in libgit2. so we undo the last commit and commit again but then it...
Wonder how we can programmatically figure that out