explain-diff
explain-diff-html.md name explain-diff-html description Use when the user asks for a rich explanation of a code change, diff, branch, or PR. Produces HTML output. Explain Diff Please make me a rich, interactive explanation of the specified code change. It should have these sections: Background: Explain the existing system relevant to this change. (You should broadly explore surrounding code for th
GitHub App の Device Flowでスコープを絞った短命なGitHubトークンを生成する - Qiita
はじめに GitHubの公式CLIであるghコマンドはべんりですが、非常に強い権限を持っているので攻撃する側から見ても魅力的です。特に gh auth token コマンドを実行するだけで簡単にGitHubトークンを抜けることは、もはや公然の秘密というか、みんな見て見ぬふりをしている大きな穴です。さらに都合の悪いことに、GitHubの公式CLIのOAuth Appで認証すると、このトークンには repo 権限があるので、自分がアクセス可能なプライベートリポジトリを読み書きでき、有効期限も設定されていないので、トークンが漏洩した場合の影響が大きくなりがちです。最近のマルウェアは個人のローカル端末を狙う攻撃が増えてきているので、GitHubトークンを抜かれた場合のダメージを如何に最小化するかというのは重要な課題です。 最初に思いつく代替案は、GitHub Fine-grained PATを使う
Automate work with routines - Claude Code Docs
Put Claude Code on autopilot. Define routines that run on a schedule, trigger on API calls, or react to GitHub events from Anthropic-managed cloud infrastructure. A routine is a saved Claude Code configuration: a prompt, one or more repositories, and a set of connectors, packaged once and run automatically. Routines execute on Anthropic-managed cloud infrastructure, so they keep working when your
GitHub Commit Status を活用した柔軟な Approve 数管理 | CyberAgent Developers Blog
目次 この記事で学べること 想定読者 はじめに GitHub の Branch Protection Rules より柔軟な制御をしたいとき、ありませんか？ Commit Status を使った approve 数制御の仕組み approval-rules の紹介と使い方 まとめ 参考リンク この記事で学べること GitHub の Branch Protection だけでは実現できない、条件付き approve 数制御の考え方 Commit Status を活用した柔軟なマージ制御の仕組み Custom GitHub Action approval-rules の導入方法と設定例 想定読者 GitHub でのコードレビュー運用を改善したいエンジニア Branch Protection の approve 数設定に不便さを感じている人 自動生成 PR やドキュメント PR のレビューフロー
Issue fields: Structured issue metadata is in public preview - GitHub Changelog
Issue fields are now available in public preview for select GitHub organizations. If you’ve been using labels like priority/p0 or severity/high to track structured data in issues, you know the limitations: no types, no validation, no consistency across repositories, and no way to report on them. Issue fields replace unstructured text in the issue body and label-based workarounds with typed, org-wi
Every GitHub Object Has Two IDs | Greptile Blog
I was recently building a feature for Greptile (an AI-powered code review tool), when I hit a weird snag with GitHub's API. The feature should have been simple: I wanted to add clickable links to GitHub PR comments, so users could jump directly from our reviews to relevant GitHub discussions. We already stored the comment IDs, so I just needed to construct the URLs. The problem was, when I tested
Hierarchy view now available in GitHub Projects - GitHub Changelog
Menu. Currently selected: 🔗 What is hierarchy view? Hierarchy view for GitHub Projects is now available in public preview. You can now view your full issue hierarchy directly in project table views, giving you clear visibility into complex work breakdowns without losing context or switching views. 🔗 What is hierarchy view? Hierarchy view lets you see the full nesting of sub-issues directly in Gi
Dependencies on issues - GitHub Changelog
Dependencies on issues are now generally available! You can now specify which issues are blocked by or blocking others, making it easy for teams to define work that must be completed before other work can begin. This has been one of our most requested features. ➕ Getting started To get started, open the Relationships section in the issues sidebar and select Mark as blocked by or Mark as blocking.
Grep a million GitHub repositories via MCP - Vercel
Grep now supports the Model Context Protocol (MCP), enabling AI apps to query a million public GitHub repositories using a standard interface. Whether you're building in Cursor, using Claude, or integrating your own agent, Grep can now serve as a searchable code index over HTTP. Link to headingWhat is the Grep MCP serverMCP is a protocol for exposing tools to large language models (LLMs). Grep’s n
Updated rate limits for unauthenticated requests - GitHub Changelog
To provide a secure and dependable experience on GitHub, we’re rolling out updates to rate limits for requests made without authentication. These changes will apply to operations like cloning repositories over HTTPS, anonymously interacting with our REST APIs, and downloading files from raw.githubusercontent.com. Why we’re updating We’ve recently observed an increase in scraping activity targeting
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
https://x.com/ericzakariasson/status/2089466749943152806
APIRadar - Real-time API Key Leak Detection