Git

Anthropic ships claude-code-action , an official GitHub Action that runs the full Claude Code runtime inside your CI/CD pipeline. It reviews pull requests, builds features from issues when someone types @claude, writes tests, updates docs, and drafts release notes. It also respects your repo’s CLAUDE.md coding rules. The runtime runs on a GitHub Actions runner, with tool use, file reads, and multi-step reasoning.

It ships with four auth backends: Anthropic API, AWS Bedrock, Google Vertex AI, and Microsoft Foundry. It also has a sister claude-code-security-review action for vuln scans, native GitLab CI/CD support, and real deployments. Deriv runs it across 700+ repos, handling 100+ PRs per week. So this has moved past the demo stage. Teams now wire it into merge gates next to linters and test suites.

You can wire a local LLM into your Git workflow to write conventional commit messages from staged diffs. The trick is a prepare-commit-msg Git hook. The hook runs git diff --cached and sends the output to Ollama . Ollama runs a model like Llama 4 Scout on a consumer GPU or Qwen3, then writes the message into the commit file for you to review. The whole setup is about 30 lines of shell or Python. It costs nothing to run, keeps your code local, and follows the Conventional Commits format. That beats the “fix stuff” messages most of us write when we just want to move on.

Running CI/CD through GitHub Actions or GitLab CI is handy until it isn’t. Free tier minute limits run out fast. Private repos cost more than you’d expect. And if your code is sensitive, you’re sending every push through someone else’s servers. Self-hosting your pipeline sidesteps all of that.

Gitea is a light, self-hosted Git service. It has added GitHub Actions-compatible workflow support through a piece called act_runner . The workflow YAML syntax is near-identical to GitHub Actions. So teams who already know that ecosystem can move over with little friction. This guide walks through a complete, production-ready CI/CD stack on Linux using Docker Compose.

git worktree lets you check out multiple branches of the same repository simultaneously into separate directories - no stashing, no cloning, no context switching overhead. Each worktree shares the same .git object store, so you get independent working trees instantly without re-downloading any history. Run git worktree add ../my-repo-hotfix hotfix/urgent-fix and you have a fully functional working tree on a separate branch, ready to build and test while your feature branch stays untouched in the original directory.

You can build a bot that labels issues, enforces PR naming, posts review comments, and triggers workflows. Write a FastAPI app that takes webhooks from GitHub or Gitea , checks the signature, and calls back to the right API. The same handler works for both forges. Header names and payload shape differ a bit, so one codebase can serve both.

How Repository Webhooks Work on GitHub and Gitea

Both GitHub and Gitea let you set up webhooks at the repo, org, or (for Gitea) system level. When an event fires (someone opens an issue, pushes a commit, opens a PR) the forge sends an HTTP POST to a URL you control. The body is JSON and describes what happened.

Claude Code, Cursor, and GitHub Copilot take three very different shots at AI-assisted coding: a terminal-native agent, an AI-first IDE, and a multi-IDE plugin. Claude Code leads on raw skill and complex multi-file work, scoring highest on SWE-bench at about 74-81%. Cursor offers the best editor experience with background agents and cloud automation. GitHub Copilot has the lowest entry price at $10/month and the widest IDE support. Most pro developers now mix two or more tools, with Claude Code plus Cursor as the top pair per the JetBrains AI Pulse survey from January 2026.