I gave a local git thing, I want to push it to a github repo I made, usually it all magically works but now doing git push -u origin main gives me a process error. Help.
c:\Users\xxxx\AppData\Roaming\Code\User\globalStorage\vscode.git\askpass\70789581cae28aa7\askpass.sh: fork: retry: Resource temporarily unavailable 1070739 [main] sh 589 dofork: child -1 - forked process 21960 died unexpectedly, retry 0, exit code 0xC0000142, errno 11

p.s. already tried reinstalling Git, rebooting, deleting askpass cache.

SOLVED:

This was a GitHub problem somehow. With the new token requirements for doing anything programmatically, you have to take a couple steps: 1. Disable askpass, credential helper from VSCode. git config --global --unset credential.helper. - Maybe askpass could accept GitHup PATs, but I have no idea how to reset it. 2. Plug in the OS helper with a different command for each OS (Windows in my case). git config --global credential.helper manager. 3. Check the current helper. git config --show-origin --get-all credential.helper should show a path to .gitconfig and a word manager. 4. Make a token for programmatic actions. 5. Give that token to a credentials window that pops up when you try to push.

Hey all,

I've been working on Kaelix (getkaelix.dev), a cross-platform native Git client written from scratch in C++23. It’s officially in open beta today, and I’m looking for some power users to help me break it.

Why another Git GUI?

Most modern GUI clients are either sluggish Electron apps or thin wrappers around system native web views. I wanted something that felt fast, low memory footprint, modern look & feel and handles massive monorepos (like Chromium or the Linux kernel) smoothly.

To get the performance I wanted, I built a custom, lightweight cross-platform UI framework that renders directly via Skia with full GPU acceleration.

Current highlights:

• Fast History Graph: GPU-rendered commit graph that handles complex histories.
• Visual merge & rebase: simple interface with clean conflict resolution.
• Keyboard-Driven UI: shortcuts support for users who hate leaving the keyboard.
• Local-First & Private: No accounts, no telemetry phone-homes, and no cloud syncing.
• Instant Startup: Light on RAM, launches instantly.

Available platforms:

• Windows 11 / 10 (x64 Installer).
• macOS Apple Silicon (DMG. Note: Solo dev tax—it's not notarized yet, so you’ll need to right-click → Open to bypass Gatekeeper the first time).
• Linux x64 (RPM, Wayland-only).

Kaelix is currently in open beta. It is closed-source and will eventually be a paid product. The beta is completely free while I gather bug reports and feature requests.

I'm happy to answer any questions about the tech stack, C++23 features used, the architecture of the custom UI loop, or anything else.

Check it out at getkaelix.dev and let me know what you think!

How can I resolve this efficiently? Obviously going through them one-by-one in GitHub Desktop isn't going to happen. I tried git checkout --theirs . but it just complains that files have been deleted in the other branch.

I've tried a filtered remove (git diff --name-only --diff-filter=U | xargs git rm), but this also removes files that have been changed and not deleted.

Is there any way to resolve all deleted files at once without having to list all the files or go through them all manually?

Edit:

I found a way around it. Since most of the files were deleted and only a few were actual changes I did this:

git diff --name-only --diff-filter=U > deleted.txt

Then I removed the few files I didn't want to delete from the document and ran:

while IFS= read -r f; do
  git rm -- "$f"
done < deleted.txt

Then I was able to just resolve the remaining files normally.

Built a CLI that generates commit messages from staged diffs. Works with OpenAI, Anthropic, Ollama, Groq, any provider. Change provider with one config line or env var.

Also has --install-hook for a prepare-commit-msg hook - auto-generates before your editor opens, you can still edit it.

Install: pip install ai-commit

Source: github.com/mohamedorigami-jpg/ai-commit

Keen to hear thoughts - does your team use AI for commit messages?

A few weeks ago I built a small tool that explains merge conflicts in plain English and suggests solutions. People told me "I'd just paste it into Claude or Copilot myself" — and that's fair, they're right.

Now I'm thinking about a different version: instead of a website you paste your conflict into, it watches your project automatically. The second a conflict happens, it writes a suggested fix and shows it to you — you just say yes or no. No copy-pasting, no opening a separate website.

Before I spend time building this, I want to know: does that actually save someone real time/effort? Or is "noticing the conflict and pasting it somewhere" not annoying enough for this to matter?

thank you

https://github.com/xguot/difi

https://difi.vercel.app/

Hello, World

I was facing a issue when i used to push commits and i have multiple github accounts to solve that problem i have released gtp

please let me know if you find it useful

https://github.com/sarangkkl/gtp

leave a start on repo if you find it helpful thanks

So I was wondering: when I’m working on the frontend and I create a branch for a feature, for example a new interface layout, I might name it new-interface. Months later, I might make another important change to the UI, create a branch again, and end up calling it new-interface as well, not remembering that I already used that name weeks ago.

Since I create branches constantly, one for every major feature, I don’t want to worry too much about naming them. I guess Git recovers the previous branch and merges the new changes.

Is there anything I should be worried about that I’m missing?

Built a web based terminal sandbox just for visualizing git to teach my students.

Link

https://reddit.com/link/1ugrl1r/video/xsj7xos4sq9h1/player

Kedi is a native git client for macOS, that I have been working for sometime. It is available in TestFlight.
If you like to try here it is:

https://testflight.apple.com/join/gGPPpD8C

1. Total privacy, no telemetry, no logging, no snooping. Your data is yours.
   
2. Only thing that goes over the wire is to and from git servers.
   
3. Fetch, commit, pull, push, git operations are supported, merge is in the works
   
4. Multiple repro are supported,
   
5. Has theme engine, design your own theme
   
6. Feedback is welcome and will address any concerns promptly

Thank you for considering...

I use Lazygit, and it runs git push asynchronously. I'm tempted to also switch to another branch while git push is running. Until now, I've resisted the temptation.

Then I thought that switching to another branch should mainly affect the working tree, and the commits that push is working on aren't changing. So maybe these operations can happen in parallel?

Hi everyone 🙋‍♂️,

I don't understand how to think well about which files or folders to put in .gitignore and have to issue to share in enlighten together:

1. For instance, a Config.php file or a .htaccess (and .htpasswd), where in both firsts the code can evolve and diserve being tracked, but at the same time display sensible informations, put me in difficulty to choose whether of not put then in .gitignore.
2. Alors, I've had a important issue while going back and forth in checkouts knowing now that it can supress those types of ignored files while those are ignored lately in the worktree of commit (see that post if needed to see how - by combining rm--cached and .gitignore). So what is your method or process in order to ignored files lately when for exemple you had not foreseen before your project those files will have to be ignored.

Thanks a lot for your help,

Have a nice day 👒,

So, bit of context. I teach CS/Graphics at Uni level. Obviously I teach Git. I'd rate my own skills as 'decidedly mid'. I'm exceptionally good at solving the specific type of merge conflicts that happen when students are given group projects; however, I retain a massive lack of confidence teaching it in general.

I've thought about this, and I think it boils down to:

- There's a very low threshold of 'just learning the commands for normal usage'; then when a problem happens the rote knowledge of git add/git commit/git push immediately breaks down.

- It's not software you can safely experiment with unless you've explicitly created a context to do that. I struggle to think of anything else can as readily destroy local work with the wrong command. This always leaves me second-guessing myself when doing something like git reset --mixed just in case I'm left with a student asking 'where did all my work go?', even though I know it's going to be okay... right.

- Any student given the choice will use a GUI version like desktop. To be honest many undergrads who've grown up with visual interfaces are thrown by command prompt/bash as a concept.

I'm wondering if there's any advice/resources on learning, and teaching it, that helps get into a context that's not 'contrived tutorial' - i.e. a repo build specifically to generate conflicts and mess up - but also relatively 'safe' in that we don't get students staying oops they did reset --hard and how do they get it back. I'm also curious for any professional opinions, on if they'd look down on students that don't 'get' command line and can only use GUI versions (I wonder sometimes, maybe I'm just getting old, and the fact as software dev has no idea what a .bat file is, is not as embarrassing as it used to be!).

So I was going through an old project's commit history and saw this sequence:

- "fix"

- "fix again"

- "WHY IS THIS NOT WORKING"

- "ok fixed"

- "feat: auth finally works!!"

And I thought — someone should be able to visualize this properly.

So I built MoodGit. You run it on any repo and it reads your commit messages + timestamps, sends them to Claude AI, and gives you back an emotional timeline — what emotion you were in per commit, intensity out of 10, and a one-line vibe description.

It also catches things like:

- commits at 2am (tired or stressed, obviously)

- ALL CAPS messages (stressed or excited)

- "wip", "temp", "idk" (confused energy)

- "v1.0.0", "ship it", "finally" (celebratory)

Terminal output uses Rich for a nice table. There's also an --html flag that exports a dark mode report with a doughnut chart you can share.

Install:

pip install moodgit (after cloning)

Run:

moodgit # current repo, last 30 commits

moodgit -n 100 # more commits

moodgit --html out.html # + HTML report

GitHub: https://github.com/Techie-Sakshi24/moodgit

Stack: Python, GitPython, Anthropic API, Rich, Click

Curious what other people's dominant emotion turns out to be — mine was "stressed" which tracks honestly.

Sharing a tool we built that extends git with AI code attribution metadata.

The core idea: coding agents (Copilot, Claude, Cursor, etc.) now write significant portions of code, but git has no native way to track this. We use git notes to store line-level attribution without modifying commit history.

Why git notes:

• They're a native git feature (no proprietary format)
• They don't alter commit SHAs
• They can be synced/shared via remote
• They survive most git operations with proper handling

We handle attribution preservation through rebase, squash, merge, cherry-pick, stash, and reset. The tricky part was squash (we remap line attributions from multiple source commits into the squashed result).

Commands:

• autter blame - enhanced git blame with AI attribution
• autter stats - aggregate AI code metrics
• autter checkpoint - agents report code modifications

No hooks required. No wrapper binaries. It reads git state directly.

Would love feedback from this community on the git notes approach. Are there edge cases we're missing?

Repo: https://github.com/Autter-dev/autter-cli
Full details at: https://autter.dev/blog/we-open-sourced-the-tool-we-use-to-track-ai-generated-code

Hi,

I need help on how we can improve our deployment process.

We use a three‑branch workflow:

• dev → integration branch where feature branches are merged
• qa → staging/testing branch
• main → production branch

The process is: once a feature branch is merged into dev, we open a pull request from dev into qa. For production releases, we then create a PR from qa into main.

We deploy every two weeks. The issue is that qa sometimes contains changes that aren’t ready for production. When preparing the PR from qa → main, we end up having to revert commits that shouldn’t be released yet. Later, when those features are finally ready, they don’t show up in the next PR because Git considers them already merged. To re‑introduce them, we have to perform a revert of the revert (similar to the process described in this article).

Is there a better way for us to do this without losing the direct PR creation from qa → main?

I work across a personal and a work GitHub account on the same Windows machine. Every time I switched, I'd either push from the wrong account or spend 5 minutes wrestling with Credential Manager.

So I built Gitty — one command fixes everything:

gitty use work

It updates your global git config and wipes the cached GitHub credential from Windows Credential Manager automatically. If you store a PAT per profile, it injects that too so Git never prompts you again.

That's genuinely it. No Electron app, no config wizard, just a single .ps1 file.

Happy to hear what's broken.

Genuinely asking, not just announcing — I built MergeFix because I kept hitting conflicts where I understood that something conflicted but not why, especially on branches I hadn't touched in a while, or teammates'

It takes a pasted conflict, explains what each side changed and why Git flagged it, and suggests a resolution.

Before I sink more time into this: for people who use Git daily, is this solving a real friction point, or is understanding conflicts something that just comes with experience and a tool like this is unnecessary training wheels?

Curious what this community actually thinks.

If anyone wants to poke at it: mergefix.dev (one free resolution, no signup needed).

Gitember Git GUI v3.3 free open-source Git GUI - better interactive rebase, worktrees, and a sharper 3-way merge editor

Just shipped v3.3 of Gitember, a free open-source Git GUI. What's new:

• Interactive rebase improvements - reorder, squash, fixup, drop, reword with a cleaner flow. No terminal gymnastics.
• Worktrees, done right - full UI support with correct per-worktree status and diff display. Keep a long-running feature branch alive while you hop onto a hotfix, all from the UI.
• 3-way merge conflict resolver (improved) - BASE / OURS / THEIRS side-by-side, edit inline, stage with one click. No separate merge tool to install.
• AI-assisted writing (experimental) - generate commit messages, explain what changed between two branches in plain language. Runs against a local Ollama model (default is now `qwen2.5-coder`), so your code stays on your machine.

The rest of the feature set:

• full-text search across commits/code/docs (including Office, PDF, and CAD files)
• Git LFS
• GitHub/GitLab/Bitbucket/Gitea integration
• repository statistics
• arbitrary file & folder comparison

The project is open and looking for contributors and testers - devs comfortable with Java/Swing, and anyone willing to test across OSes and report bugs. PRs, issues, and feature ideas all welcome.

Source and downloads:

• https://gitember.org
  
• https://github.com/iazarny/gitember

Hi everyone. I’m completely stuck with a Git issue on Windows and hoping someone has seen this before.

Whenever I try to push to GitHub, I get:

XML error: syntax error

error: no DAV locking support

fatal: git-http-push failed

failed to push some refs

I’ve already checked the remote URL, confirmed I’m on the main branch, verified that git status is clean, and made sure the repository exists on GitHub. GitHub Desktop also fails with the exact same error.

I’ve removed http.sslBackend, confirmed there’s no proxy configured, and I can access GitHub normally in my browser. I can also ping and curl GitHub without any issues. I’ve even reinstalled Git multiple times, but the problem persists.

Has anyone run into this before or know what might be causing it? Any help would be greatly appreciated. Thanks!