Brendan Forster
Brendan Forster
Desktop received a report about our use of `git status` interfering with a user's preferred config: https://github.com/desktop/desktop/issues/3734 I looked at the behaviour of `git status` and it doesn't seem to...
There are some issues like #72 and #164 that require making changes to Git. The rough idea is this: - keep working from known stable Git versions as a submodule...
Make the details from [this release](https://github.com/desktop/dugite-native/releases/tag/v2.18.0-1) easier to find, combine that with the details in #105, and end up with a friendly guide for downstream packagers to know what shared...
Reported downstream: https://github.com/desktop/dugite/issues/154 This requires: - a FreeBSD CI platform (or equivalent) that can be used to build PRs and validate changes - the ability to publish tagged builds to...
Preview builds are available from Microsoft here: https://github.com/Microsoft/git/releases There's MinGit-esque releases in there, which we could slipstream in here for experimental support. I haven't thought much about the work to...
MinGit does not contain a version of `gpg` to use for managing commit signing. I think we can live without this for macOS and Linux (cc @smashwilson for feels).
- [ ] test how this works with local group policy enforced - [ ] documentation
From #27 > Need to add a test for dodgy non-null-terminated data, but I'm not sure the best way to actually get this into the registry in the first place,...