找到 1634 篇相关文章
GitHub热门项目 | Learn how to design large-scale systems. Prep for the system design interview. Includes Anki flashcards. | Stars: 360,291 | 138 stars today | 语言: Python
GitHub热门项目 | DeepSeek-native AI coding agent for your terminal. Engineered around prefix-cache stability — leave it running. | Stars: 29,612 | 877 stars today | 语言: Go
GitHub热门项目 | Fast Rust library for PDF inspection, classification, and text extraction. Intelligently detects scanned vs text-based PDFs to enable smart routing decisions. | Stars: 6,819 | 1,769 stars today | 语言: Rust
GitHub热门项目 | Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨 | Stars: 15,462 | 133 stars this week | 语言: TypeScript
GitHub热门项目 | Open-source media request and discovery manager for Jellyfin, Plex, and Emby. | Stars: 12,106 | 127 stars this week | 语言: TypeScript
GitHub热门项目 | Rust‑first, cross‑platform wgpu/WebGPU renderer exposed to Python for fast, headless 3D rendering. Built in Rust, shipped as Python wheels. | Stars: 558 | 10 stars today | 语言: Rust
GitHub热门项目 | A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/ | Stars: 13,405 | 6 stars today | 语言: Rust
GitHub热门项目 | 🦎 a tool to build and deploy software on many servers 🦎 | Stars: 11,769 | 10 stars today | 语言: Rust
GitHub热门项目 | Open Brain — The infrastructure layer for your thinking. One database, one AI gateway, one chat channel — any AI plugs in. No middleware, no SaaS. | Stars: 4,357 | 14 stars today | 语言: TypeScript
GitHub热门项目 | Story Creation AI Agent for novel, scripts, translation, interactive games, and IP content | Stars: 8,614 | 55 stars today | 语言: TypeScript
GitHub热门项目 | 基于Dineshkarthik的项目， 电报视频下载，电报资源下载，跨平台，支持web查看下载进度 ，支持bot下发指令下载，支持下载已经加入的私有群但是限制下载的资源， telegram media download,Download media files from a telegram conversation/chat/channel up to 2GiB per file | Stars: 5,440 | 7 stars today | 语言: JavaScript
GitHub热门项目 | Character Generator based on Universal-LPC-Spritesheet | Stars: 1,539 | 10 stars today | 语言: JavaScript
GitHub热门项目 | 洛雪音乐源 | Stars: 7,541 | 36 stars today | 语言: JavaScript
GitHub热门项目 | Comprehensive production pipeline for quad-modal AI filmmaking with Seedance 2.0 | Stars: 5,846 | 101 stars today | 语言: Python
GitHub热门项目 | A unified trading API with more than 100 crypto exchanges and prediction markets in JavaScript / TypeScript / Python / C# / PHP / Go / Java | Stars: 43,480 | 17 stars today | 语言: Python
GitHub热门项目 | Netflix-level subtitle cutting, translation, alignment, and even dubbing - one-click fully automated AI video subtitle team | Netflix级字幕切割、翻译、对齐、甚至加上配音，一键全自动视频搬运AI字幕组 | Stars: 18,012 | 48 stars today | 语言: Python
The problem is not the code I build Flutter apps. A normal feature touches four layers at once. Models and json parsing Repository and API client State management Screens and widgets When I ship that as one branch, the pull request is somewhere between 1,000 and 4,000 lines. And then one of two things happens. Either the reviewer opens 40 files, scrolls for ten minutes, and writes "looks good". That is not a review. That is a signature. Or the reviewer does the job properly, takes three days, and leaves a comment on the models file. Now every screen above it has to change. The writing was fast. The review was slow. That is the real bottleneck. The old workaround You already know it. Split the work into branches yourself. git checkout -b feat/booking-models git checkout -b feat/booking-repo # branched off models git checkout -b feat/booking-state # branched off repo git checkout -b feat/booking-ui # branched off state This works for about one day. Then a reviewer asks for a change in feat/booking-models , and you rebase three branches by hand. Then it happens again. Most people give up and go back to the giant branch. What stacked pull requests change On July 30 2026 GitHub put stacked pull requests into public preview. The idea is small. A stack is an ordered series of pull requests. Each pull request targets the one below it instead of targeting main . Only the bottom one targets main . PR #4 screens and widgets -> targets PR #3 PR #3 cubits and state -> targets PR #2 PR #2 repository and api -> targets PR #1 PR #1 models and parsing -> targets main Because each pull request only contains its own layer, opening PR #3 shows you the state management diff and nothing else. Not the models. Not the widgets. The Flutter example Say I am building a booking flow. Here is the same feature, sliced. PR 1 - models and json parsing. Around 190 lines. Targets main. class Booking { final String id ; final DateTime startsAt ; final BookingStatus status ; const Booking ({ required
GitHub热门项目 | A modern JavaScript utility library delivering modularity, performance, & extras. | Stars: 61,273 | 26 stars this week | 语言: JavaScript
GitHub热门项目 | Build your own AI SRE agents. The open source toolkit for the AI era. | Stars: 9,680 | 536 stars this week | 语言: Python
GitHub热门项目 | The official Python SDK for Model Context Protocol servers and clients | Stars: 23,833 | 127 stars this week | 语言: Python