pull request を利用した開発ワークフローの話しですが、あんまりプルリの話ししてないし、コードレビュー的なお話しが多いです…。
pull request を利用した開発ワークフローの話しですが、あんまりプルリの話ししてないし、コードレビュー的なお話しが多いです…。
Dangling Tree A dangling tree is a directory tree of files that was not attached to a commit. These are rarely interesting, and often caused by merge conflicts. Inspect these files with git ls-tree -r SHA-1 Stashes Finally, you may have stashed the data instead of committing it and then forgotten about it. You can use the git stash list command or inspect them visually using: Misplaced Another opt
The future is already here — it's just not very evenly distributed. At my work, we have been using a Git branching strategy based on Vincent Driessen’s successful Git branching model. Over all, the strategy that Vincent proposes is very good and may work perfectly out of the box for many cases. However, since starting to use it I have noticed a few problems as time goes on: a LOT of branches – Si
米Microsoftは3月21日、オープンソースソフトウェア向けのホスティングサービス「CodePlex」でGitをサポートすることを発表した。これにより開発者は、Microsoft Team Foundation Server（TFS）、Subversion、Mercurial、Gitからバージョン管理システムを選択できるようになる。 CodePlexはMicrosoftが2006年に開始したオープンソースソフトウェアプロジェクトのホスティングサイト。CodePlexはこれまで、中央型のバージョン管理システムとしてTFSおよびSubversionを、分散バージョン管理システムとしてMercurialをサポートしてきたが、今回新たにGitもサポートする。 MicrosoftのMark Groves氏はブログでGitサポートの理由について、「コミュニティからの要望が最も多い機能の1つだった」
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
About the book This book uses practical examples to explain version control with both centralized and decentralized systems. Topics covered include: Basic version control commands and concepts Introduction to Distributed Version Control Systems (DVCS) Advanced branching workflows Strengths and weaknesses of DVCS vs. centralized tools Best practices How distributed version control works under the
Matt Chaput wrote on November 21, 2011 at 9:18 am: Thanks for confirming that my decision to stick with hg was correct. IMHO git is a human factors horrowshow. Brandon Philips wrote on November 21, 2011 at 9:20 am : Kernel developers only frown on rebase in public trees meant for others to consume. Lots of us use it to make clean commits before pushing where people expect stability. kumar303 wrote
IntroductionStGIT is a Python application that provides functionality similar to quilt (i.e. pushing/popping patches to/from a stack) using GIT instead of 'diff' and 'patch'. StGIT stores its patches in a GIT repository as normal GIT commit objects.StGIT is not an SCM interface on top of GIT. For standard SCM operations, either use GIT's porcelain commands or the Cogito tool.StGIT is available for
Once you get past the prototyping, unit tests and the code what you have is the only real documentation anyone is going to update.— Something that sounds like “Code Complete” or another McConnell classic. A good software development process is all about communication.— 37 Signals about Basecamp. Thank you, Captain Obvious— Anonymous lolcat. Communication is the mantra of two of my long-time feeds.
Commit message style guide for Git The first line of a commit message serves as a summary. When displayed on the web, it's often styled as a heading, and in emails, it's typically used as the subject. As such, you should capitalize it and omit any trailing punctuation. Aim for about 50 characters, give or take, otherwise it may be painfully truncated in some contexts. Write it, along with the rest
思い浮かんだGitのTipsを列挙してみました。 gitのコマンドをで補完する git-completion.bash を入れると、でコマンドの補完が効くようになります。 また、PS1の設定を行うと現在のブランチ名が常にbash上に表示されるようになります。 （Windowsの場合、msysgit は標準で入ってます） contrib/completion/git-completion.bash - GitHub インストール方法（引用） # To use these routines: # # 1) Copy this file to somewhere (e.g. ~/.git-completion.sh). # 2) Add the following line to your .bashrc/.zshrc: # source ~/.git-completion.sh # # 3)
19 Apr 2008 I want to take a moment to elaborate on what makes a well formed commit message. I think the best practices for commit message formatting is one of the little details that makes Git great. Understandably, some of the first commits to rails.git have messages of the really-long-line variety, and I want to expand on why this is a poor practice. Here’s a model Git commit message: Capitaliz
Background: At the Mozilla AllHands in Sept2011, I was surprised to find that my proposed session on git was accepted, and even more surprised at how well this session was attended! The room was full of people from all different groups across Mozilla. And boy, were people passionate. The slides don’t capture the lively back-forth discussions, but this is obviously a topic that people care deeply a
追記：たくさんブクマしていただいて驚いております。ブクマコメントだと、やはり git push -f は反則だろという意見がサイレントマジョリティのようですが、そこはそれ、自 己 責 任 追記２(2011/11/07)：commit messageをミスった場合について訂正しました。 git rebase -i で直近のコミットを "edit" にして修正すると、 「--amend使えや」と言われるようです。 gitのコミットをしくじった時の対処法について、一覧性の高いまとめがなかったので作りました。正確さは保証できないので、コマンド名ヒントに自分でググって下さい ほかのやり方があるよ、間違ってるよ等のご指摘歓迎です。 派閥別 gitでコミットミスった時のまとめ ｜ ├─ 一人で使ってるよ ｜ ｜ ｜ ├─ 手元に変更を取り戻したいよ(1)（そうだね、add忘れだね派） ｜ ｜
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
