r/git

Hello, guys. So in previous post I saw all your advices, but problem is the same. So I take screenshots to make it more easy to understand.

On the photo 1 I did the first commit and all was good as usually.

Photo 2 — I pushed my project on github with my commit.

On photo 3 I add some changes and a command "git add ."

Photo 4 — I try to commit and get this in the terminal. They just saying that there's nothing to commit.

Photo 5 — a command "git status" and nothing changed again!

What should I do?

P.S. as I said in previous post, I tried in intellij idea and all worked. Also I tried it many times again and in intellij al works good! So I really don't know why this problem keeps happening in VS code.

Hey everyone,

Let’s be honest for a second. We’ve all seen (or written) commit histories that look something like this:

- fix: bug
- fix: actually fix the bug
- fix: forgot semicolon
- please work
- asdfghjkl
- final_final_v2_really_working

Your team lead sighs. Git blame becomes a game of Russian roulette. And when it’s time to write a release changelog, nobody has any idea what actually changed.

I got tired of staring blankly at a 500-line diff on Friday afternoon trying to craft the perfect Conventional Commit message, so I built Cogit — a lightweight CLI and TUI tool written in Rust.

What does it actually do?

You stage your files with git add, run cogit, and it inspects your staged diff to generate clean, structured Conventional Commits (feat:, fix:, refactor:, chore:, etc.).

Here’s why it’s not just another Python wrapper script:

1. Dual-Pane TUI (cogit --tui): Built with ratatui. You get a syntax-highlighted diff on the left and an editable textarea on the right. You can scroll through your changes, edit the generated message in-place, press [r] to regenerate with a hint (e.g. "focus on the auth refactor"), or hit [e] to drop straight into $EDITOR.
2. Multi-Provider AI: Works out of the box with Google Gemini, OpenAI, Grok (xAI), Groq, or 100% locally with Ollama if you don't want your code leaving your machine.
3. Lockfile & Noise Sanitization: It automatically strips Cargo.lock, package-lock.json, and binary blobs from the diff payload before sending it to the LLM so you don't burn tokens on 15,000 lines of hash changes.
4. Safe by Design: It invokes git commit -F under the hood via a temporary buffer, meaning it preserves your existing pre-commit hooks, GPG/SSH signatures, and git config.
5. Detailed Mode (-d): If you need more than a single-line summary, -d generates a conventional subject line along with bulleted rationale for PRs and complex reviews.

Links & Code

It's completely free and open source under the MIT license:

• GitHub: https://github.com/shadowmkj/cogit
• Crates.io: https://crates.io/crates/cogit

I’d love to hear your feedback, feature requests, or constructive roasts. Let me know what you think!

Also any contributions are welcome 🦀

You click an action → see the Git command → see what changed.

There’s also a Learning Mode for beginners with interactive practice and real Git scenarios.

Here’s a quick demo of what I’ve built so far 👇
This is just a quick demo, not the full app. I’ll be adding the rest of the Git commands and more features before the first release.

The project will be open source, and I’m hoping we can keep adding to it and turn it into a useful Git tool for everyone.

Still early, so I’d love to hear your feedback.

I’m trying to understand whether I’m hitting a configuration problem, an account/product limitation, or a current limitation of ChatGPT App Classic.

I use ChatGPT heavily alongside Codex for a fairly large software project hosted in a private GitHub repository. What I want is relatively simple: I would like ChatGPT App Classic to have direct read access to the GitHub repo so I can discuss the current codebase, architecture, PRs, migrations, etc. without constantly moving context between ChatGPT and Codex.

The strange part is that GitHub itself is working correctly.

On my Mac:

• gh is installed and current (2.97.0)
• gh auth status shows that I’m authenticated successfully
• Git operations use HTTPS
• Token has repo, workflow, read:org, etc.
• I can fetch/push normally
• Codex can work with the repository
• GitHub CLI can create/manage PRs

I have also reauthenticated from Terminal using:

gh auth login -h github.com

Authentication completes successfully.

So this doesn’t appear to be a GitHub authentication or repository-permissions problem.

The problem is specifically ChatGPT App Classic. I can’t get it to reliably access the same GitHub repository directly, even though other OpenAI tooling can work with it.

This is becoming a significant workflow issue because I use ChatGPT for the higher-level architecture/governance side of the project and Codex for repository execution. Ideally the workflow would be:

ChatGPT: inspect current repo/PR state → reason about architecture → give execution instructions
Codex: implement/test/commit/PR
ChatGPT: inspect the resulting repo/PR → review → determine next step

Instead, I often have to manually paste Codex reports back into ChatGPT because ChatGPT Classic cannot inspect the repository itself. On a large project with lots of migrations, tests, ADRs and governance artifacts, that becomes both inefficient and potentially error-prone.

I’m specifically trying to determine:

1. Is direct GitHub access currently supported in ChatGPT App Classic?
2. Is GitHub access dependent on the ChatGPT mode/model being used?
3. Does the GitHub App/connector only work in certain experiences such as Deep Research or Agent Mode?
4. Is there a difference between GitHub access in the web app and the macOS Classic app?
5. If GitHub is already connected to the OpenAI account, is there some way to force/re-authorize the connection for Classic?
6. Has anyone had GitHub working in one ChatGPT surface but unavailable in another and actually fixed it?
7. Is there any diagnostic page/log that shows whether ChatGPT itself has permission to access a particular private repository?

I’m not looking for help configuring GitHub CLI. That side is confirmed working. I’m specifically trying to get ChatGPT itself to see the repository.

If anyone has a working setup with ChatGPT App Classic + private GitHub repositories, I’d be very interested in exactly how you configured it, including plan, GitHub App/plugin configuration, ChatGPT mode, and whether you’re using web or macOS.

Even confirmation that “this currently isn’t supported in Classic” would be useful, because at least I’d stop troubleshooting something that cannot presently be fixed.

Has anyone solved this?

We just released GitComet 0.2.0 after roughly two months of work on our open-source Git GUI.

A lot of the work wasn't about building huge new features. It was fixing dozens of small workflows and interaction details based on feedback from GitHub, Reddit, and other channels.

During the 0.1.x releases, our main goal was feature parity with existing Git GUI tools. With 0.2.x, we're starting to move beyond that: refining the UI, making it feel more modern, and experimenting with workflows that aren't as common in traditional Git clients.

One example is smaller laptop screens. We wanted the UI to remain useful without everything feeling cramped, so the side panel can now be minimized while keeping its functionality easily accessible.

We also received quite a bit of feedback that the interface didn't feel modern enough. That pushed us to rethink spacing, hierarchy, interactions, and the overall visual style rather than just adding more functionality.

Some of the bigger changes in 0.2.0:

• New visual design and UI refinements
• Rebase and interactive rebase support
• Browse and edit repository files directly inside GitComet
• Browse files as they existed at a specific point in Git history
• Worktree changes shown alongside the Git log/history graph
• Git log filtering by author
• Improved merge/conflict tooling, including better conflict-marker selection
• Many more right-click context menus and actions throughout the UI
• Better responsiveness for smaller screens

Probably the biggest lesson from these two months is that feature implementation is increasingly the easy part. Making dozens of features work together naturally is where a surprising amount of engineering time still goes.

GitComet is written in Rust + GPUI, open source, and free for personal and commercial use.

Website: https://gitcomet.dev/
Repository: https://github.com/Auto-Explore/GitComet

Hi everyone! I'm a developer from Cambodia and for the past months I've been building AngKorGit, a free, open-source (MIT) Git client for macOS, Windows, and Linux — named after Angkor Wat.

I love GUI clients like GitKraken but wanted something lightweight and completely free. So it's built with Rust + libgit2 and the system webview (Tauri) instead of Electron — the whole download is ~12 MB, and the commit graph stays smooth on 100k-commit repos.

What it does today: visual conflict resolver (pick lines from A/B, edit the result by hand), interactive rebase, stage by file/hunk/line, drag-and-drop merge/rebase, undo/redo, built-in terminal, 16 themes, and optional AI commit messages via CLIs you already have — no account, no telemetry.

GitHub: https://github.com/cheat2001/angkorgit

Site: https://angkorgit.app

macOS: brew install --cask cheat2001/tap/angkorgit

Would genuinely love feedback from people who live in Git all day — what would you need before using something like this daily?

I wanted to share a project I'm working on: git-calendar.org - a privacy-focused calendar that uses a standard Git repository as storage instead of relying on a traditional backend server. It lets users choose where their data is stored. No more google/apple/microslop owning your schedule.

Key features:

• Git-powered - calendar data live in plain Git repo (full history, easy backups, works offline)
• No central server or backend - the client talks directly to any Git remote (GitHub, GitLab, Codeberg...)
• End-to-end encryption so you can host it on untrusted providers
• Slick web UI with keyboard shortcuts and more
• iCalendar compatibility so it's easy to switch

Core is written in Go (compiled to WASM for the web).
The web client uses Vue.js.
It's ready for Android and IOS apps. Feel free to build one!

Try it: https://git-calendar.org
Source: https://github.com/git-calendar

Would love feedback from people who care about Git-based tools and data ownership. Also you can support the project with a star and follow on GitHub, to let me know I should continue working on it!