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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Show HN: Git-fired tells you who was fired / added based on Git log

40 点作者 michaellee8将近 4 年前

5 条评论

jdikatz将近 4 年前
Cool idea —- also makes me realize that if GitHub can see commit history of all repos, then Microsoft has a lot of partly identified info on personnel movement across teams within lots of companies and also across companies
评论 #27414670 未加载
评论 #27419884 未加载
michaellee8将近 4 年前
It tells you what new names existed or old names removed in your commit log during the specified periods. Suppport comparing based on name+email or name only. Support recursively looping through all subdirectries.<p>Sample usage:<p># git-fired 2021&#x2F;06&#x2F;01 2021&#x2F;05&#x2F;01 -single<p># git-fired 2021&#x2F;06&#x2F;01 2021&#x2F;05&#x2F;01 -multi<p># git-fired 2021&#x2F;06&#x2F;01 2021&#x2F;05&#x2F;01 -single -name<p># git-fired 2021&#x2F;06&#x2F;01 2021&#x2F;05&#x2F;01 -single -name<p>compares the commit log of the current repo (-single) or all git repos under current directory (-multi) during 2021&#x2F;05&#x2F;01 to 2021&#x2F;06&#x2F;01 and 2021&#x2F;06&#x2F;01 to now, by default compares using name+email, pass -name to compare using name only.
toomuchtodo将近 4 年前
Consider extending this to identify heavy churn or lack thereof. Repeated short tenures in an org is useful signal.
officialjunk将近 4 年前
how about those that leave a company without being fired?
评论 #27414798 未加载
评论 #27416101 未加载
评论 #27415565 未加载
评论 #27414888 未加载
ok123456将近 4 年前
Problem with this is that git identities aren&#x27;t unique. If I do a quick commit from another machine it will likely have garbage for the name and email based on GECOS and the hostname.
评论 #27415783 未加载