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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Successful GitHub Development

63 点作者 b14ck大约 13 年前

5 条评论

davvid大约 13 年前
Another interesting thing I've found is that packagers really prefer tarballs. They can checksum them. They don't need to download your full history, etc.<p>The tarballs automatically produced by github have names that are annoying and makes things harder for packagers, so I find myself creating "make dist" targets and uploading the result to github. Is there an API for file uploads? (that would be sweet!)<p>I do wish there was a way to provide a format string that would tell github the basename to use for tarballs.<p>If you are jquery and your project is jquery your tarballs look like jquery-jquery-v1.2.3-g654321.tar.gz and the directory basename is the same.<p>If they added the ability to configure it per-repo and used "{{ user }}-{{ repo }}-{{ tag }}-{{ sha1 }}" as the default then they could keep backwards compat and let folks configure it to their liking. It's one of my very few github peeves.
emillon大约 13 年前
git-flow is not needed, especially for small projects. For most repositories, developing on and sending pull requests to master is acceptable.
评论 #3842230 未加载
Palomides大约 13 年前
rather more extensive and general, but somewhat related book (Producing Open Source Software): <a href="http://producingoss.com/a" rel="nofollow">http://producingoss.com/a</a>
andrewflnr大约 13 年前
Why is using the builtin wiki a bad idea?
评论 #3842675 未加载
评论 #3842159 未加载
cnbeuiwx大约 13 年前
So like...<p>1. Write Official Documentation (booooring)<p>2. Use Git Flow (version management, boooooring)<p>3. Publish Test Runs (oh, testing.. thats fun right? no...ok...)<p>4. Use GitHub Issues (....)<p>5. Have fun. (yes!!)<p>Ill take one number 5 please. And 1-4 is why Im not a professional programmer.