I have been maintaining hub, the command-line git extension, for 10 years. After 2,100 issues and pull requests closed, 18k+ stars on GitHub, and countless hours invested in it, I thought it might be fitting to reflect on its unlikely past, share a bit about my process working on it, and address the future of GitHub on the command line. In 2010, the entire implementation of hub 1.0 sat in a single
$ gh issue list gh pr status gh pr checkout gh pr create gh pr checks gh release create gh repo view gh alias set View and filter a repository’s open issues. Check on the status of your pull requests. Check out pull requests locally. Create a new pull request. View your pull requests’ checks. Create a new release. View repository READMEs. Create a shortcut for a gh command.
Caching, Parallelism ♥ Docker multi-stage builds 12 Feb 2020 Most of the resources on the internet I ran across while reading about multi-stage builds tout the benefit of smaller images. While it is a great feature, I’ve had the experience of benefiting from other, possibly underrated, side-effects of multi-stage builds: caching and parallelism. In my opinion1, these two offer so much better user
AI & MLLearn about artificial intelligence and machine learning across the GitHub ecosystem and the wider industry. Generative AILearn how to build with generative AI. GitHub CopilotChange how you work with GitHub Copilot. LLMsEverything developers need to know about LLMs. Machine learningMachine learning tips, tricks, and best practices. How AI code generation worksExplore the capabilities and be
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く