找到 1111 篇相关文章
Install and configure LSP servers for GitHub Copilot CLI, replacing brute-force grep/decompile with real code intelligence. The post Give GitHub Copilot CLI real code intelligence with language servers appeared first on The GitHub Blog .
GitHub热门项目 | Concise, consistent, and legible badges in SVG and raster format | Stars: 26,767 | 55 stars this week | 语言: JavaScript
GitHub热门项目 | All-in-one Mail & Collaboration server. Secure, scalable and fluent in every protocol (IMAP, JMAP, SMTP, CalDAV, CardDAV, WebDAV). | Stars: 13,123 | 17 stars today | 语言: Rust
GitHub热门项目 | Low-level cross-platform audio I/O library in Rust | Stars: 3,797 | 3 stars today | 语言: Rust
GitHub热门项目 | ☄🌌️ The minimal, blazing-fast, and infinitely customizable prompt for any shell! | Stars: 58,253 | 99 stars today | 语言: Rust
GitHub热门项目 | ✨ Making your shell magical | Stars: 30,170 | 56 stars today | 语言: Rust
GitHub热门项目 | Search infrastructure for AI | Stars: 28,350 | 48 stars today | 语言: Rust
GitHub热门项目 | A minimal, secure Python interpreter written in Rust for use by AI | Stars: 7,519 | 165 stars today | 语言: Rust
GitHub热门项目 | An extremely fast Python linter and code formatter, written in Rust. | Stars: 47,898 | 17 stars today | 语言: Rust
GitHub热门项目 | The first open-source harness builder for AI coding. Make AI coding deterministic and repeatable. | Stars: 22,310 | 38 stars today | 语言: TypeScript
GitHub热门项目 | Spec-driven development (SDD) for AI coding assistants. | Stars: 54,010 | 290 stars today | 语言: TypeScript
GitHub热门项目 | 🧡 Folo is the AI RSS Reader | Stars: 38,447 | 36 stars today | 语言: TypeScript
GitHub热门项目 | Create and share 3D architectural projects. | Stars: 16,576 | 69 stars today | 语言: TypeScript
GitHub热门项目 | One brain for all your agents | Stars: 637 | 47 stars today | 语言: TypeScript
GitHub热门项目 | Stop renting your intelligence. Own it with AnythingLLM. Everything you need for a powerful local-first agent experience | Stars: 61,365 | 71 stars today | 语言: JavaScript
GitHub热门项目 | A curated collection of practical AI projects implementing OCR systems, RAG, AI agents, and other AI use cases. | Stars: 1,908 | 125 stars today | 语言: Python
GitHub热门项目 | Advanced DNS tunneling VPN for censorship bypass, optimized beyond DNSTT and SlipStream with low-overhead ARQ, resolver load balancing, high packet-loss stability and speed. | Stars: 4,987 | 92 stars today | 语言: Go
GitHub热门项目 | 🕵️♂️ Collect a dossier on a person by username from 3000+ sites | Stars: 31,717 | 261 stars today | 语言: Python
GitHub热门项目 | Production-grade engineering skills for AI coding agents. | Stars: 50,403 | 781 stars today | 语言: Shell
Your CI was green last Friday. Today, the payments test is failing. Somewhere between Friday's merge and now, 47 commits landed on main . Which one broke it? Most developers answer this the wrong way: they scroll through git log , check out suspicious commits one by one, and run the test manually. An hour later, they're still guessing. There's a command built for this exact problem. It's called git bisect , and once you learn it, you'll never debug regressions the old way again. How bisect works git bisect is a binary search across your commit history. You tell Git two things: A good commit (a known point where the bug didn't exist) A bad commit (a known point where the bug exists — usually HEAD ) Git then checks out the commit halfway between them. You test. You mark it as good or bad. Git narrows the range by half. Repeat. With 47 commits between "good" and "bad", it takes at most 6 steps (log₂ 47) to find the exact commit that introduced the bug. Versus checking every commit manually, that's the difference between 5 minutes and an hour. The manual workflow # Start a bisect session $ git bisect start # Mark the current state (HEAD) as bad $ git bisect bad # Mark a known-good commit $ git bisect good a3f1d22 # Bisecting: 23 revisions left to test after this (roughly 5 steps) # [7e4b9c1] refactor: extract payment validator # Git has checked out a commit in the middle. Run your test. $ npm test -- --grep "payments" # Test passed — mark this commit as good $ git bisect good # Bisecting: 11 revisions left to test after this (roughly 4 steps) # [b2d8e11] feat: add retry logic to payment API # Test failed — mark this commit as bad $ git bisect bad # ... continue until Git announces the first bad commit: # b2d8e11 is the first bad commit # commit b2d8e11 # Author: leo@company.com # Date: Tue Apr 15 11:42:03 # feat: add retry logic to payment API # Done — reset to where you started $ git bisect reset In 6 commands, you know exactly which commit broke the tests. No guessing