今日已更新 119 条资讯 | 累计 20985 条内容
关于我们

标签：#git

找到 1125 篇相关文章

AI 资讯

I Abandoned an MCP Server for 3 Months. Then I Finished It in 48 Hours with GitHub Copilot

This is a submission for the GitHub Finish-Up-A-Thon Challenge The Project That Got Away Three months ago, I started building something I was genuinely excited about: devto-mcp — a Model Context Protocol (MCP) server that would let AI agents interact with Dev.to's API natively. No more cobbling together curl commands. No more writing custom wrapper scripts for every AI tool. Just a clean, standards-compliant MCP server that any AI agent could plug into. I had a vision: an AI agent that could autonomously research trending topics, draft articles, publish them, track engagement, and iterate — all through a single protocol. The kind of thing that sounds simple until you actually sit down to build it. I got about 40% of the way through. Then life happened. A client project deadline. A cross-country move. A laptop that decided to corrupt its SSD at the worst possible time. The repo sat there on GitHub, collecting digital dust, with half-implemented tool functions and a README that promised way more than the code delivered. Sound familiar? If you've been a developer for more than a year, you have at least one of these ghost repos. That ambitious side project you were so sure you'd finish "next weekend." The one with the clever name and the detailed architecture doc but barely functional code. Two weeks ago, I saw the GitHub Finish-Up-A-Thon announcement. I looked at my list of abandoned repos. And I thought: it's time. What I Built: devto-mcp devto-mcp is a Model Context Protocol server that exposes Dev.to's entire API as MCP-compatible tools. If you're not familiar with MCP, it's the protocol that lets AI assistants like Claude, Cursor, and other coding agents interact with external tools in a standardized way. Think of it as a universal adapter between AI models and the services developers actually use. Here's the problem it solves: Every time you want an AI agent to interact with Dev.to — whether it's searching for articles, publishing a post, checking analytics, or ma

2026-06-02 原文 →
AI 资讯

GitHub Copilot for Engineers: Getting Better Results

Original post: GitHub Copilot for Engineers: Getting Better Results GitHub Copilot moved to usage-based billing in June 2026, dropping the flat subscription model that made monthly costs predictable. For teams using it heavily across multiple projects, that shift puts a premium on being deliberate: reaching for the right model, keeping prompts focused, and building a configuration that produces good results without a lot of back-and-forth iteration. Many of us install the extension, start with the defaults, and only tune settings later. The defaults are a reasonable starting point, but they are not a full configuration. A small investment in setup changes how much you get out of every request on an ordinary working day, and that matters more now that each request has a cost attached. This guide covers the full path: getting the tooling in place, choosing models with cost in mind, layering global and project-level rules, and building out instructions, agents, and skills that make Copilot predictable across different kinds of work. Architecture overview Diagram fallback for Dev.to. View the canonical article for the full version: https://sourcier.uk/blog/github-copilot-for-engineers Before you start Subscription and VS Code extension You need an active GitHub Copilot subscription. Plans are available at individual, business, and enterprise tiers at github.com/features/copilot . Once active, all tools use your GitHub account credentials. The GitHub Copilot extension for VS Code is the primary day-to-day interface. Install it from the Extensions panel or via the CLI: code --install-extension GitHub.copilot The extension provides inline completions as you type, Copilot Chat in the sidebar, inline chat on any selection via Cmd+I / Ctrl+I , agent mode for multi-step tasks, and multi-file edits with a single review step. Defaults keep improving, so avoid cargo-culting old setting lists. Focus on non-default tweaks that improve signal quality and control usage: Setting Value

2026-06-02 原文 →
AI 资讯

Running Claude in CI: A GitHub Actions + Claude Code SDK Auto-PR-Reviewer That Costs $0.03 per Review

⚠️ この記事はアフィリエイト広告（プロモーション）を含みます。リンク先で発生した収益の一部が運営者に支払われますが、読者の購入価格には一切影響ありません。 By the end of this article you will have a GitHub Actions workflow that, on every pull_request , runs the Claude Code SDK headlessly, reads only the diff, and posts inline review comments via the GitHub API. I'll show the exact YAML and Python that run in my own repos, the token math that keeps each review at roughly $0.03, and the three failures that cost me a weekend before it worked. Why I stopped piping the full repo into Claude on GitHub Actions My first version did the obvious thing: clone the repo, concatenate every changed file in full, and ask Claude to "review this PR." It worked on toy PRs and exploded on real ones. A 9-file refactor sent ~48,000 input tokens and the review drifted into commentary about code the PR didn't touch. The fix that changed the economics: feed Claude the unified diff with 3 lines of context , not the files. A git diff against the merge base is typically 5–15x smaller than the files it touches. On claude-haiku-4-5 , a median PR in my projects now costs about $0.028 per review (measured across 60 PRs: 4,100 input tokens + 900 output tokens average). The expensive version was hitting $0.40+ on Sonnet because file context dominated. The other lesson: the diff alone is not enough context to judge correctness, but it is enough to catch the 80% of review nits that humans waste time on — unhandled errors, missing null checks, off-by-one, leftover debug prints, secrets in code. So I scoped the prompt to exactly that, and told it to stay silent when unsure. Silence is a feature; a reviewer that comments on everything gets muted by the team within a week. The GitHub Actions workflow YAML that triggers Claude on pull_request This is the full .github/workflows/claude-review.yml . It runs on every PR, restores a uv-cached venv, and calls a Python entrypoint. Note the permissions block — without pull-requests: write the comment-posting step fails with a 403 that GitH

2026-06-02 原文 →
AI 资讯

Facelinked - a truly *social* media

This is a submission for the GitHub Finish-Up-A-Thon Challenge What I Built I started this project as a way to escape the noise of social media we have today and to focus on what matters. It was a personal project at first and I just wanted to get an uncluttered messaging working. After a while a few friends of mine started looking into it and liked the vision as well. Then I received a notification of the event and that excitement of finishing it up got all over me - I felt like a kid again. Demo Because I want to have control over my data, I self host the version on a small microcontroller, which is more than sufficient for me and my friends. To get a sneak peak at how it looks, check out this . (Be aware that this is not functional as there is no server connected) I made some demo accounts to give a sense of how the app looks and feels: The Comeback Story Because I had the messaging already working, I had to mainly implement the rest of the features, including enhanced profiles, networks and posts creation. Another thing I really had to work on was the design. Before, it was mainly a black and white testing ground - something every end user would be scared of. My Experience with GitHub Copilot I am really not talented in terms of designing a usable interface. However, my friends really didn't want to use a half-baked up command line application. Copilot really helped me achieve that polished look. Just to give a glimpse of how it feels, one friend of mine even described it as an enhancing feature when navigating through the tabs. Furthermore, although it mostly was bug free, "It worked, until it didn't". Sometimes I spent hours fixing or rather finding some annoying bugs. And because Copilot is a real expert in these languages, it was quite a moment when it guided me towards finding the mistakes I made.

2026-06-02 原文 →
← 上一页 下一页 →