TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Tidying up after Pull Requests

105 点作者 janerik超过 12 年前

9 条评论

DTrejo超过 12 年前
Check out my command-line tool, rotten: <a href="https://github.com/dtrejo/rotten" rel="nofollow">https://github.com/dtrejo/rotten</a><p><pre><code> npm install -g rotten </code></pre> It helps you discover<p>* Which remote branches are empty (all code is in master), also outputs a command to delete them all.<p>* Which remote branches still have lots of code that needs to be merged<p>* How long remote branches have been waiting to be merged.<p>.<p>Why is this useful?<p>* discover which projects are languishing<p>* discover which engineers are unhappy that their code is not being reviewed/merged<p>* discover how effective your development process is
评论 #4870300 未加载
jordanthoms超过 12 年前
To tidy up a repository with lots of merged branches, you can use this script: <a href="http://snippets.freerobby.com/post/491644841/remove-merged-branches-in-git" rel="nofollow">http://snippets.freerobby.com/post/491644841/remove-merged-b...</a><p>Although it seems the best approach would be to actually keep the branch pointers around, but have a way of hiding them to reduce the clutter
评论 #4868776 未加载
fmstephe超过 12 年前
On an Enterprise project I was on recently this was a real problem. With about 12 distinct and large (5-10 developers per team) all working on a single git repo, the lingering branches were out of control. They had built up over more than a year of abuse.<p>I think this issue is worth thinking about. For projects with a single owner or a small core set of contributors taking pull requests it is manageable. But when the responsibility is distributed, especially in the degenerate culture of Enterprise Java, uncontrolled branching can make git usage miserable.<p>The real problem was that we were using Git like an SVN server. But it was really interesting to see how bad it can be when branch pruning is not considered upfront.<p>Great feature github :)
评论 #4867982 未加载
STRML超过 12 年前
Way to go Github! I think it is quite clear that pull requests are the best feature of Github and a boon to the OSS community in general. This feature is a welcome tightening.
guynamedloren超过 12 年前
Biggest pain point associated with code reviews are the lingering branches. So glad this has finally been bundled into Github. Thanks Github!
unwiredben超过 12 年前
Excellent... I've been manually sweeping for these about once a month on Enyo, but it will be nice to have it part of our merge flow.
评论 #4868051 未加载
meastham超过 12 年前
It always baffled me that this feature didn't exist before. I'm glad they implemented it.
dochtman超过 12 年前
So when I merge a pull request on Github, it's rebased, not actually merged?
评论 #4869990 未加载
cmaggard超过 12 年前
I've been waiting for this for quite some time now. Kudos!