| CARVIEW |
Select Language
HTTP/2 302
server: nginx
date: Wed, 23 Jul 2025 20:47:43 GMT
content-type: text/plain; charset=utf-8
content-length: 0
x-archive-redirect-reason: found capture at 20090127014749
location: https://web.archive.org/web/20090127014749/https://github.com/guides/feature-requests.atom
server-timing: captures_list;dur=0.641903, exclusion.robots;dur=0.025555, exclusion.robots.policy;dur=0.013307, esindex;dur=0.013305, cdx.remote;dur=75.073948, LoadShardBlock;dur=399.628429, PetaboxLoader3.datanode;dur=218.376633, PetaboxLoader3.resolve;dur=111.384092
x-app-server: wwwb-app218
x-ts: 302
x-tr: 503
server-timing: TR;dur=0,Tw;dur=0,Tc;dur=0
set-cookie: SERVER=wwwb-app218; path=/
x-location: All
x-rl: 0
x-na: 0
x-page-cache: MISS
server-timing: MISS
x-nid: DigitalOcean
referrer-policy: no-referrer-when-downgrade
permissions-policy: interest-cohort=()
HTTP/2 200
server: nginx
date: Wed, 23 Jul 2025 20:47:44 GMT
content-type: application/atom+xml; charset=utf-8
content-length: 1226802
x-archive-orig-server: nginx/0.6.31
x-archive-orig-date: Tue, 27 Jan 2009 01:47:47 GMT
x-archive-orig-connection: close
x-archive-orig-status: 200 OK
x-archive-orig-x-runtime: 5516ms
x-archive-orig-etag: "dc56ba6d3eb59b82c16e1c913e4859df"
x-archive-orig-cache-control: private, max-age=0, must-revalidate
x-archive-orig-content-length: 1226802
cache-control: max-age=1800
x-archive-guessed-content-type: text/xml
x-archive-guessed-charset: utf-8
memento-datetime: Tue, 27 Jan 2009 01:47:49 GMT
link: ; rel="original", ; rel="timemap"; type="application/link-format", ; rel="timegate", ; rel="first memento"; datetime="Thu, 24 Jul 2008 07:25:25 GMT", ; rel="prev memento"; datetime="Thu, 24 Jul 2008 07:25:25 GMT", ; rel="memento"; datetime="Tue, 27 Jan 2009 01:47:49 GMT", ; rel="last memento"; datetime="Tue, 27 Jan 2009 01:47:49 GMT"
content-security-policy: default-src 'self' 'unsafe-eval' 'unsafe-inline' data: blob: archive.org web.archive.org web-static.archive.org wayback-api.archive.org athena.archive.org analytics.archive.org pragma.archivelab.org wwwb-events.archive.org
x-archive-src: 52_7_20090126232520_crawl101-c/52_7_20090127014609_crawl101.arc.gz
server-timing: captures_list;dur=0.676753, exclusion.robots;dur=0.033095, exclusion.robots.policy;dur=0.016920, esindex;dur=0.015607, cdx.remote;dur=42.340223, LoadShardBlock;dur=350.411855, PetaboxLoader3.datanode;dur=193.692412, PetaboxLoader3.resolve;dur=237.819342, load_resource;dur=194.755455
x-app-server: wwwb-app218
x-ts: 200
x-tr: 635
server-timing: TR;dur=0,Tw;dur=0,Tc;dur=0
x-location: All
x-rl: 0
x-na: 0
x-page-cache: MISS
server-timing: MISS
x-nid: DigitalOcean
referrer-policy: no-referrer-when-downgrade
permissions-policy: interest-cohort=()
accept-ranges: bytes
tag:github.com,2008:/guides/feature-requests
GitHub Guides - Feature Requests
2008-12-03T19:56:28-08:00
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-12-03T19:56:28-08:00
Feature Requests - version 118
Wed Dec 03 19:56:28 -0800 2008
<p>Got an idea? Use the <a href="https://github.com/contact">contact form</a> or <a href="https://support.github.com/">the support site</a></p>
<p>Looking for help? Try #github in irc.freenode.net or the <a href="https://groups.google.com/group/github/">Google Group</a>.</p>
<p>Find a bug? Use the <a href="https://github.com/contact">contact form</a> or <a href="https://support.github.com/">the support site</a></p>
davetron5000
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-12-03T19:56:12-08:00
Feature Requests - version 117
Wed Dec 03 19:56:12 -0800 2008
<p>Got an idea? Use the <a href="https://github.com/contact">contact form</a> or https://support.github.com/</p>
<p>Looking for help? Try #github in irc.freenode.net or the <a href="https://groups.google.com/group/github/">Google Group</a>.</p>
<p>Find a bug? Use the <a href="https://github.com/contact">contact form</a> or https://support.github.com/</p>
davetron5000
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-12-03T19:55:09-08:00
Feature Requests - version 116
Wed Dec 03 19:55:09 -0800 2008
<p>Got an idea? Use the <a href="https://github.com/contact">contact form</a></p>
<p>Looking for help? Try #github in irc.freenode.net or the <a href="https://groups.google.com/group/github/">Google Group</a>.</p>
<p>Find a bug? Use the <a href="https://github.com/contact">contact form</a></p>
davetron5000
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-13T14:30:03-07:00
Feature Requests - version 115
Thu Mar 13 14:30:03 -0700 2008
<p>Got an idea? Please visit our <a href="https://logicalawesome.lighthouseapp.com/projects/8570/home">Lighthouse tracker</a>. It’s free to make an account and will help us keep track of things better.</p>
<p>Looking for help? Try #github in irc.freenode.net or the <a href="https://groups.google.com/group/github/">Google Group</a>.</p>
<p>Find a bug? <a href="https://logicalawesome.lighthouseapp.com/projects/8570/home">There’s a tracker for that</a>, too.</p>
<p><a href="https://tinyurl.com/2zbe73">Open feature request list</a>.</p>
defunkt
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-12T17:05:38-07:00
Feature Requests - version 114
Wed Mar 12 17:05:38 -0700 2008
<p>Got an idea? Please visit our <a href="https://logicalawesome.lighthouseapp.com/projects/8570/home">Lighthouse tracker</a>. It’s free to make an account and will help us keep track of things better.</p>
<p>Looking for help? Try #github in irc.freenode.net or the <a href="https://groups.google.com/group/github/">Google Group</a>.</p>
<p>Find a bug? <a href="https://logicalawesome.lighthouseapp.com/projects/8570/home">There’s a tracker for that</a>, too.</p>
<p><a href="https://logicalawesome.lighthouseapp.com/projects/8570-github/tickets/bins/5381">Open feature request list</a>.</p>
defunkt
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-12T17:05:29-07:00
Feature Requests - version 113
Wed Mar 12 17:05:29 -0700 2008
<p>Got an idea? Please visit our <a href="https://logicalawesome.lighthouseapp.com/projects/8570/home">Lighthouse tracker</a>. It’s free to make an account and will help us keep track of things better.</p>
<p>Looking for help? Try #github in irc.freenode.net or the <a href="https://groups.google.com/group/github/">Google Group</a>.</p>
<p>Find a bug? “There’s a tracker for that”: https://logicalawesome.lighthouseapp.com/projects/8570/home, too.</p>
<p><a href="https://logicalawesome.lighthouseapp.com/projects/8570-github/tickets/bins/5381">Open feature request list</a>.</p>
defunkt
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-12T08:50:17-07:00
Feature Requests - version 112
Wed Mar 12 08:50:17 -0700 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>It would be nice to have banner logos for links to repos and personal areas.</h3>
<h3>Add way to discuss commits. Point is nicely wrapped up in this post at Novemberain:</h3>
<p>https://novemberain.com/2008/3/12/what-is-missing-from-github</p>
<h3>Automatically maintain a git mirror of an svn repository</h3>
<p>This is related to the rejected request below, but more useful. Allow creation of a git mirror of a subversion repository and periodically update it (possibly with a ping <span class="caps">URL</span> that will schedule an immediate update). If there are branches/tags, mirror those too as local branches, not just trunk.</p>
<h3>Don’t have “Cancel” next to “Send” when composing a PM</h3>
<p>Easy to click the wrong one and lose text. “[Send] or <a>Cancel</a>” is probably better, or at least a confirmation on the cancel button.</p>
<h3>Add a web hook for pull requests</h3>
<p>Just a simple json <span class="caps">POST</span> to a <span class="caps">URL</span>, like the post-receive-hook. It would be useful for e.g: posting the request to a mailing list or automatically create a patch review.</p>
<h3>Edit active and not “current” revision on wiki</h3>
<p>When pressing “edit” on a wiki page, edit the viewed revision rather than the latest. This makes restoring old revisions easier, or using an old revision as base for new edits.</p>
<h3>Make it easier to make a navigatable wiki-page with anchors and link list</h3>
<p>Like I have done manually at <a href="https://github.com/dag/amazing/wikis/configuration/22">this page</a>.</p>
<h3>Attempt to match the commit Author to the github profile’s username, name, and email.</h3>
<p>Right now I own a project but my git author name is my full name spelled out, so it my github name, but not my github username. And it’s not showing me as author of my commits.</p>
<h3>Provide ability to add Google Analytics tracking code to repo home page</h3>
<p>Allow owners to analyze the viewership of their project by providing the ability to specify a snippet of <span class="caps">HTML</span>/JS for the google tracking code. If the snippet of JS is undesireable to be inserted directly into the page body you could instead embed this code on the site and embed just the user’s unique tracking code into that JS for them. Having visibility into who is viewing project is powerful.</p>
<p>Code looks like:</p>
<p>< script src=”https://www.google-analytics.com/urchin.js” type=”text/javascript”>
</ script>
< script type=”text/javascript”>
_uacct = “INSERT_UNIQUE_USER_TRACKING_ID_HERE”;
urchinTracker();
</ script></p>
<h3>Resend invitation</h3>
<p>Right now (2008-03-08), if you send an invitation out and it gets “lost,” there is no resend capability—and entering in the email address again gives you a message saying it can’t send another. Maybe this should be more friendly, and just resend?</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h3>Combine the From you and For you News Feed</h3>
<p>What the title says.</p>
<h3>Just a simple label that says “read-only” next to the public clone <span class="caps">URL</span></h3>
<p>I know there’s a note about this in the <span class="caps">FAQ</span>, but for those new to git, it could be helpful.</p>
<h3>Render URLs in commit messages</h3>
<p>I see Textile and markdown syntax isn’t going to be done. Simple url rendering would be nice though.</p>
<h3>Diff link in <span class="caps">RSS</span> when a wiki is updated</h3>
<p>because when I’m notified of a change I want to know what changed.</p>
<h3>Repository search should search anywhere in the name</h3>
<p>For example, searching for ‘rails’ does not return koz-rails; only projects that begin with the string ‘rails’.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h3><del>Forgotten Password Link</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
timburks
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-11T19:51:37-07:00
Feature Requests - version 111
Tue Mar 11 19:51:37 -0700 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Add way to discuss commits. Point is nicely wrapped up in this post at Novemberain:</h3>
<p>https://novemberain.com/2008/3/12/what-is-missing-from-github</p>
<h3>Automatically maintain a git mirror of an svn repository</h3>
<p>This is related to the rejected request below, but more useful. Allow creation of a git mirror of a subversion repository and periodically update it (possibly with a ping <span class="caps">URL</span> that will schedule an immediate update). If there are branches/tags, mirror those too as local branches, not just trunk.</p>
<h3>Don’t have “Cancel” next to “Send” when composing a PM</h3>
<p>Easy to click the wrong one and lose text. “[Send] or <a>Cancel</a>” is probably better, or at least a confirmation on the cancel button.</p>
<h3>Add a web hook for pull requests</h3>
<p>Just a simple json <span class="caps">POST</span> to a <span class="caps">URL</span>, like the post-receive-hook. It would be useful for e.g: posting the request to a mailing list or automatically create a patch review.</p>
<h3>Edit active and not “current” revision on wiki</h3>
<p>When pressing “edit” on a wiki page, edit the viewed revision rather than the latest. This makes restoring old revisions easier, or using an old revision as base for new edits.</p>
<h3>Make it easier to make a navigatable wiki-page with anchors and link list</h3>
<p>Like I have done manually at <a href="https://github.com/dag/amazing/wikis/configuration/22">this page</a>.</p>
<h3>Attempt to match the commit Author to the github profile’s username, name, and email.</h3>
<p>Right now I own a project but my git author name is my full name spelled out, so it my github name, but not my github username. And it’s not showing me as author of my commits.</p>
<h3>Provide ability to add Google Analytics tracking code to repo home page</h3>
<p>Allow owners to analyze the viewership of their project by providing the ability to specify a snippet of <span class="caps">HTML</span>/JS for the google tracking code. If the snippet of JS is undesireable to be inserted directly into the page body you could instead embed this code on the site and embed just the user’s unique tracking code into that JS for them. Having visibility into who is viewing project is powerful.</p>
<p>Code looks like:</p>
<p>< script src=”https://www.google-analytics.com/urchin.js” type=”text/javascript”>
</ script>
< script type=”text/javascript”>
_uacct = “INSERT_UNIQUE_USER_TRACKING_ID_HERE”;
urchinTracker();
</ script></p>
<h3>Resend invitation</h3>
<p>Right now (2008-03-08), if you send an invitation out and it gets “lost,” there is no resend capability—and entering in the email address again gives you a message saying it can’t send another. Maybe this should be more friendly, and just resend?</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h3>Combine the From you and For you News Feed</h3>
<p>What the title says.</p>
<h3>Just a simple label that says “read-only” next to the public clone <span class="caps">URL</span></h3>
<p>I know there’s a note about this in the <span class="caps">FAQ</span>, but for those new to git, it could be helpful.</p>
<h3>Render URLs in commit messages</h3>
<p>I see Textile and markdown syntax isn’t going to be done. Simple url rendering would be nice though.</p>
<h3>Diff link in <span class="caps">RSS</span> when a wiki is updated</h3>
<p>because when I’m notified of a change I want to know what changed.</p>
<h3>Repository search should search anywhere in the name</h3>
<p>For example, searching for ‘rails’ does not return koz-rails; only projects that begin with the string ‘rails’.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h3><del>Forgotten Password Link</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
michaelklishin
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-11T17:54:55-07:00
Feature Requests - version 110
Tue Mar 11 17:54:55 -0700 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Automatically maintain a git mirror of an svn repository</h3>
<p>This is related to the rejected request below, but more useful. Allow creation of a git mirror of a subversion repository and periodically update it (possibly with a ping <span class="caps">URL</span> that will schedule an immediate update). If there are branches/tags, mirror those too as local branches, not just trunk.</p>
<h3>Don’t have “Cancel” next to “Send” when composing a PM</h3>
<p>Easy to click the wrong one and lose text. “[Send] or <a>Cancel</a>” is probably better, or at least a confirmation on the cancel button.</p>
<h3>Add a web hook for pull requests</h3>
<p>Just a simple json <span class="caps">POST</span> to a <span class="caps">URL</span>, like the post-receive-hook. It would be useful for e.g: posting the request to a mailing list or automatically create a patch review.</p>
<h3>Edit active and not “current” revision on wiki</h3>
<p>When pressing “edit” on a wiki page, edit the viewed revision rather than the latest. This makes restoring old revisions easier, or using an old revision as base for new edits.</p>
<h3>Make it easier to make a navigatable wiki-page with anchors and link list</h3>
<p>Like I have done manually at <a href="https://github.com/dag/amazing/wikis/configuration/22">this page</a>.</p>
<h3>Attempt to match the commit Author to the github profile’s username, name, and email.</h3>
<p>Right now I own a project but my git author name is my full name spelled out, so it my github name, but not my github username. And it’s not showing me as author of my commits.</p>
<h3>Provide ability to add Google Analytics tracking code to repo home page</h3>
<p>Allow owners to analyze the viewership of their project by providing the ability to specify a snippet of <span class="caps">HTML</span>/JS for the google tracking code. If the snippet of JS is undesireable to be inserted directly into the page body you could instead embed this code on the site and embed just the user’s unique tracking code into that JS for them. Having visibility into who is viewing project is powerful.</p>
<p>Code looks like:</p>
<p>< script src=”https://www.google-analytics.com/urchin.js” type=”text/javascript”>
</ script>
< script type=”text/javascript”>
_uacct = “INSERT_UNIQUE_USER_TRACKING_ID_HERE”;
urchinTracker();
</ script></p>
<h3>Resend invitation</h3>
<p>Right now (2008-03-08), if you send an invitation out and it gets “lost,” there is no resend capability—and entering in the email address again gives you a message saying it can’t send another. Maybe this should be more friendly, and just resend?</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h3>Combine the From you and For you News Feed</h3>
<p>What the title says.</p>
<h3>Just a simple label that says “read-only” next to the public clone <span class="caps">URL</span></h3>
<p>I know there’s a note about this in the <span class="caps">FAQ</span>, but for those new to git, it could be helpful.</p>
<h3>Render URLs in commit messages</h3>
<p>I see Textile and markdown syntax isn’t going to be done. Simple url rendering would be nice though.</p>
<h3>Diff link in <span class="caps">RSS</span> when a wiki is updated</h3>
<p>because when I’m notified of a change I want to know what changed.</p>
<h3>Repository search should search anywhere in the name</h3>
<p>For example, searching for ‘rails’ does not return koz-rails; only projects that begin with the string ‘rails’.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h3><del>Forgotten Password Link</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
pd
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-11T14:48:52-07:00
Feature Requests - version 109
Tue Mar 11 14:48:52 -0700 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Automatically maintain a git mirror of an svn repository</h3>
<p>This is related to the rejected request below, but more useful. Allow creation of a git mirror of a subversion repository and periodically update it (possibly with a ping <span class="caps">URL</span> that will schedule an immediate update). If there are branches/tags, mirror those too as local branches, not just trunk.</p>
<h3>Don’t have “Cancel” next to “Send” when composing a PM</h3>
<p>Easy to click the wrong one and lose text. “[Send] or <a>Cancel</a>” is probably better, or at least a confirmation on the cancel button.</p>
<h3>Add a web hook for pull requests</h3>
<p>Just a simple json <span class="caps">POST</span> to a <span class="caps">URL</span>, like the post-receive-hook. It would be useful for e.g: posting the request to a mailing list or automatically create a patch review.</p>
<h3>Edit active and not “current” revision on wiki</h3>
<p>When pressing “edit” on a wiki page, edit the viewed revision rather than the latest. This makes restoring old revisions easier, or using an old revision as base for new edits.</p>
<h3>Make it easier to make a navigatable wiki-page with anchors and link list</h3>
<p>Like I have done manually at <a href="https://github.com/dag/amazing/wikis/configuration/22">this page</a>.</p>
<h3>Attempt to match the commit Author to the github profile’s username, name, and email.</h3>
<p>Right now I own a project but my git author name is my full name spelled out, so it my github name, but not my github username. And it’s not showing me as author of my commits.</p>
<h3>Provide ability to add Google Analytics tracking code to repo home page</h3>
<p>Allow owners to analyze the viewership of their project by providing the ability to specify a snippet of <span class="caps">HTML</span>/JS for the google tracking code. If the snippet of JS is undesireable to be inserted directly into the page body you could instead embed this code on the site and embed just the user’s unique tracking code into that JS for them. Having visibility into who is viewing project is powerful.</p>
<p>Code looks like:</p>
<p>< script src=”https://www.google-analytics.com/urchin.js” type=”text/javascript”>
</ script>
< script type=”text/javascript”>
_uacct = “INSERT_UNIQUE_USER_TRACKING_ID_HERE”;
urchinTracker();
</ script></p>
<h3>Resend invitation</h3>
<p>Right now (2008-03-08), if you send an invitation out and it gets “lost,” there is no resend capability—and entering in the email address again gives you a message saying it can’t send another. Maybe this should be more friendly, and just resend?</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h3>Combine the From you and For you News Feed</h3>
<p>What the title says.</p>
<h3>Just a simple label that says “read-only” next to the public clone <span class="caps">URL</span></h3>
<p>I know there’s a note about this in the <span class="caps">FAQ</span>, but for those new to git, it could be helpful.</p>
<h3>Render URLs in commit messages</h3>
<p>I see Textile and markdown syntax isn’t going to be done. Simple url rendering would be nice though.</p>
<h3>Diff link in <span class="caps">RSS</span> when a wiki is updated</h3>
<p>because when I’m notified of a change I want to know what changed.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h3><del>Forgotten Password Link</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
bmizerany
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-11T14:45:01-07:00
Feature Requests - version 108
Tue Mar 11 14:45:01 -0700 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Automatically maintain a git mirror of an svn repository</h3>
<p>This is related to the rejected request below, but more useful. Allow creation of a git mirror of a subversion repository and periodically update it (possibly with a ping <span class="caps">URL</span> that will schedule an immediate update). If there are branches/tags, mirror those too as local branches, not just trunk.</p>
<h3>Don’t have “Cancel” next to “Send” when composing a PM</h3>
<p>Easy to click the wrong one and lose text. “[Send] or <a>Cancel</a>” is probably better, or at least a confirmation on the cancel button.</p>
<h3>Add a web hook for pull requests</h3>
<p>Just a simple json <span class="caps">POST</span> to a <span class="caps">URL</span>, like the post-receive-hook. It would be useful for e.g: posting the request to a mailing list or automatically create a patch review.</p>
<h3>Edit active and not “current” revision on wiki</h3>
<p>When pressing “edit” on a wiki page, edit the viewed revision rather than the latest. This makes restoring old revisions easier, or using an old revision as base for new edits.</p>
<h3>Make it easier to make a navigatable wiki-page with anchors and link list</h3>
<p>Like I have done manually at <a href="https://github.com/dag/amazing/wikis/configuration/22">this page</a>.</p>
<h3>Attempt to match the commit Author to the github profile’s username, name, and email.</h3>
<p>Right now I own a project but my git author name is my full name spelled out, so it my github name, but not my github username. And it’s not showing me as author of my commits.</p>
<h3>Provide ability to add Google Analytics tracking code to repo home page</h3>
<p>Allow owners to analyze the viewership of their project by providing the ability to specify a snippet of <span class="caps">HTML</span>/JS for the google tracking code. If the snippet of JS is undesireable to be inserted directly into the page body you could instead embed this code on the site and embed just the user’s unique tracking code into that JS for them. Having visibility into who is viewing project is powerful.</p>
<p>Code looks like:</p>
<p>< script src=”https://www.google-analytics.com/urchin.js” type=”text/javascript”>
</ script>
< script type=”text/javascript”>
_uacct = “INSERT_UNIQUE_USER_TRACKING_ID_HERE”;
urchinTracker();
</ script></p>
<h3>Resend invitation</h3>
<p>Right now (2008-03-08), if you send an invitation out and it gets “lost,” there is no resend capability—and entering in the email address again gives you a message saying it can’t send another. Maybe this should be more friendly, and just resend?</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h3>Combine the From you and For you News Feed</h3>
<p>What the title says.</p>
<h3>Just a simple label that says “read-only” next to the public clone <span class="caps">URL</span></h3>
<p>I know there’s a note about this in the <span class="caps">FAQ</span>, but for those new to git, it could be helpful.</p>
<h3>Render URLs in commit messages</h3>
<p>I see Textile and markdown syntax isn’t going to be done. Simple url rendering would be nice though.</p>
<h3>Give diff link in <span class="caps">RSS</span> when a wiki is updated</h3>
<p>When I see a wiki has changed and I follow the link to the wiki. The first thing I’m interested in is “What changed?”</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h3><del>Forgotten Password Link</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
bmizerany
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-10T14:50:01-07:00
Feature Requests - version 107
Mon Mar 10 14:50:01 -0700 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Automatically maintain a git mirror of an svn repository</h3>
<p>This is related to the rejected request below, but more useful. Allow creation of a git mirror of a subversion repository and periodically update it (possibly with a ping <span class="caps">URL</span> that will schedule an immediate update). If there are branches/tags, mirror those too as local branches, not just trunk.</p>
<h3>Don’t have “Cancel” next to “Send” when composing a PM</h3>
<p>Easy to click the wrong one and lose text. “[Send] or <a>Cancel</a>” is probably better, or at least a confirmation on the cancel button.</p>
<h3>Add a web hook for pull requests</h3>
<p>Just a simple json <span class="caps">POST</span> to a <span class="caps">URL</span>, like the post-receive-hook. It would be useful for e.g: posting the request to a mailing list or automatically create a patch review.</p>
<h3>Edit active and not “current” revision on wiki</h3>
<p>When pressing “edit” on a wiki page, edit the viewed revision rather than the latest. This makes restoring old revisions easier, or using an old revision as base for new edits.</p>
<h3>Make it easier to make a navigatable wiki-page with anchors and link list</h3>
<p>Like I have done manually at <a href="https://github.com/dag/amazing/wikis/configuration/22">this page</a>.</p>
<h3>Attempt to match the commit Author to the github profile’s username, name, and email.</h3>
<p>Right now I own a project but my git author name is my full name spelled out, so it my github name, but not my github username. And it’s not showing me as author of my commits.</p>
<h3>Provide ability to add Google Analytics tracking code to repo home page</h3>
<p>Allow owners to analyze the viewership of their project by providing the ability to specify a snippet of <span class="caps">HTML</span>/JS for the google tracking code. If the snippet of JS is undesireable to be inserted directly into the page body you could instead embed this code on the site and embed just the user’s unique tracking code into that JS for them. Having visibility into who is viewing project is powerful.</p>
<p>Code looks like:</p>
<p>< script src=”https://www.google-analytics.com/urchin.js” type=”text/javascript”>
</ script>
< script type=”text/javascript”>
_uacct = “INSERT_UNIQUE_USER_TRACKING_ID_HERE”;
urchinTracker();
</ script></p>
<h3>Resend invitation</h3>
<p>Right now (2008-03-08), if you send an invitation out and it gets “lost,” there is no resend capability—and entering in the email address again gives you a message saying it can’t send another. Maybe this should be more friendly, and just resend?</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h3>Combine the From you and For you News Feed</h3>
<p>What the title says.</p>
<h3>Just a simple label that says “read-only” next to the public clone <span class="caps">URL</span></h3>
<p>I know there’s a note about this in the <span class="caps">FAQ</span>, but for those new to git, it could be helpful.</p>
<h3>Render URLs in commit messages</h3>
<p>I see Textile and markdown syntax isn’t going to be done. Simple url rendering would be nice though.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h3><del>Forgotten Password Link</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
rubymaverick
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-10T12:15:11-07:00
Feature Requests - version 106
Mon Mar 10 12:15:11 -0700 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Automatically maintain a git mirror of an svn repository</h3>
<p>This is related to the rejected request below, but more useful. Allow creation of a git mirror of a subversion repository and periodically update it (possibly with a ping <span class="caps">URL</span> that will schedule an immediate update). If there are branches/tags, mirror those too as local branches, not just trunk.</p>
<h3>Don’t have “Cancel” next to “Send” when composing a PM</h3>
<p>Easy to click the wrong one and lose text. “[Send] or <a>Cancel</a>” is probably better, or at least a confirmation on the cancel button.</p>
<h3>Add a web hook for pull requests</h3>
<p>Just a simple json <span class="caps">POST</span> to a <span class="caps">URL</span>, like the post-receive-hook. It would be useful for e.g: posting the request to a mailing list or automatically create a patch review.</p>
<h3>Edit active and not “current” revision on wiki</h3>
<p>When pressing “edit” on a wiki page, edit the viewed revision rather than the latest. This makes restoring old revisions easier, or using an old revision as base for new edits.</p>
<h3>Make it easier to make a navigatable wiki-page with anchors and link list</h3>
<p>Like I have done manually at <a href="https://github.com/dag/amazing/wikis/configuration/22">this page</a>.</p>
<h3>Attempt to match the commit Author to the github profile’s username, name, and email.</h3>
<p>Right now I own a project but my git author name is my full name spelled out, so it my github name, but not my github username. And it’s not showing me as author of my commits.</p>
<h3>Provide ability to add Google Analytics tracking code to repo home page</h3>
<p>Allow owners to analyze the viewership of their project by providing the ability to specify a snippet of <span class="caps">HTML</span>/JS for the google tracking code. If the snippet of JS is undesireable to be inserted directly into the page body you could instead embed this code on the site and embed just the user’s unique tracking code into that JS for them. Having visibility into who is viewing project is powerful.</p>
<p>Code looks like:</p>
<p>< script src=”https://www.google-analytics.com/urchin.js” type=”text/javascript”>
</ script>
< script type=”text/javascript”>
_uacct = “INSERT_UNIQUE_USER_TRACKING_ID_HERE”;
urchinTracker();
</ script></p>
<h3>Resend invitation</h3>
<p>Right now (2008-03-08), if you send an invitation out and it gets “lost,” there is no resend capability—and entering in the email address again gives you a message saying it can’t send another. Maybe this should be more friendly, and just resend?</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h3>Just a simple label that says “read-only” next to the public clone <span class="caps">URL</span></h3>
<p>I know there’s a note about this in the <span class="caps">FAQ</span>, but for those new to git, it could be helpful.</p>
<h3>Render URLs in commit messages</h3>
<p>I see Textile and markdown syntax isn’t going to be done. Simple url rendering would be nice though.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h3><del>Forgotten Password Link</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
jrun
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-10T07:03:19-07:00
Feature Requests - version 105
Mon Mar 10 07:03:19 -0700 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Automatically maintain a git mirror of an svn repository</h3>
<p>This is related to the rejected request below, but more useful. Allow creation of a git mirror of a subversion repository and periodically update it (possibly with a ping <span class="caps">URL</span> that will schedule an immediate update). If there are branches/tags, mirror those too as local branches, not just trunk.</p>
<h3>Don’t have “Cancel” next to “Send” when composing a PM</h3>
<p>Easy to click the wrong one and lose text. “[Send] or <a>Cancel</a>” is probably better, or at least a confirmation on the cancel button.</p>
<h3>Add a web hook for pull requests</h3>
<p>Just a simple json <span class="caps">POST</span> to a <span class="caps">URL</span>, like the post-receive-hook. It would be useful for e.g: posting the request to a mailing list or automatically create a patch review.</p>
<h3>Edit active and not “current” revision on wiki</h3>
<p>When pressing “edit” on a wiki page, edit the viewed revision rather than the latest. This makes restoring old revisions easier, or using an old revision as base for new edits.</p>
<h3>Make it easier to make a navigatable wiki-page with anchors and link list</h3>
<p>Like I have done manually at <a href="https://github.com/dag/amazing/wikis/configuration/22">this page</a>.</p>
<h3>Attempt to match the commit Author to the github profile’s username, name, and email.</h3>
<p>Right now I own a project but my git author name is my full name spelled out, so it my github name, but not my github username. And it’s not showing me as author of my commits.</p>
<h3>Provide ability to add Google Analytics tracking code to repo home page</h3>
<p>Allow owners to analyze the viewership of their project by providing the ability to specify a snippet of <span class="caps">HTML</span>/JS for the google tracking code. If the snippet of JS is undesireable to be inserted directly into the page body you could instead embed this code on the site and embed just the user’s unique tracking code into that JS for them. Having visibility into who is viewing project is powerful.</p>
<p>Code looks like:</p>
<p>< script src=”https://www.google-analytics.com/urchin.js” type=”text/javascript”>
</ script>
< script type=”text/javascript”>
_uacct = “INSERT_UNIQUE_USER_TRACKING_ID_HERE”;
urchinTracker();
</ script></p>
<h3>Resend invitation</h3>
<p>Right now (2008-03-08), if you send an invitation out and it gets “lost,” there is no resend capability—and entering in the email address again gives you a message saying it can’t send another. Maybe this should be more friendly, and just resend?</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h3>Just a simple label that says “read-only” next to the public clone <span class="caps">URL</span></h3>
<p>I know there’s a note about this in the <span class="caps">FAQ</span>, but for those new to git, it could be helpful.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h3><del>Forgotten Password Link</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
kballard
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-10T03:29:18-07:00
Feature Requests - version 104
Mon Mar 10 03:29:18 -0700 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Don’t have “Cancel” next to “Send” when composing a PM</h3>
<p>Easy to click the wrong one and lose text. “[Send] or <a>Cancel</a>” is probably better, or at least a confirmation on the cancel button.</p>
<h3>Add a web hook for pull requests</h3>
<p>Just a simple json <span class="caps">POST</span> to a <span class="caps">URL</span>, like the post-receive-hook. It would be useful for e.g: posting the request to a mailing list or automatically create a patch review.</p>
<h3>Edit active and not “current” revision on wiki</h3>
<p>When pressing “edit” on a wiki page, edit the viewed revision rather than the latest. This makes restoring old revisions easier, or using an old revision as base for new edits.</p>
<h3>Make it easier to make a navigatable wiki-page with anchors and link list</h3>
<p>Like I have done manually at <a href="https://github.com/dag/amazing/wikis/configuration/22">this page</a>.</p>
<h3>Attempt to match the commit Author to the github profile’s username, name, and email.</h3>
<p>Right now I own a project but my git author name is my full name spelled out, so it my github name, but not my github username. And it’s not showing me as author of my commits.</p>
<h3>Provide ability to add Google Analytics tracking code to repo home page</h3>
<p>Allow owners to analyze the viewership of their project by providing the ability to specify a snippet of <span class="caps">HTML</span>/JS for the google tracking code. If the snippet of JS is undesireable to be inserted directly into the page body you could instead embed this code on the site and embed just the user’s unique tracking code into that JS for them. Having visibility into who is viewing project is powerful.</p>
<p>Code looks like:</p>
<p>< script src=”https://www.google-analytics.com/urchin.js” type=”text/javascript”>
</ script>
< script type=”text/javascript”>
_uacct = “INSERT_UNIQUE_USER_TRACKING_ID_HERE”;
urchinTracker();
</ script></p>
<h3>Resend invitation</h3>
<p>Right now (2008-03-08), if you send an invitation out and it gets “lost,” there is no resend capability—and entering in the email address again gives you a message saying it can’t send another. Maybe this should be more friendly, and just resend?</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h3>Just a simple label that says “read-only” next to the public clone <span class="caps">URL</span></h3>
<p>I know there’s a note about this in the <span class="caps">FAQ</span>, but for those new to git, it could be helpful.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h3><del>Forgotten Password Link</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
henrik
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-10T03:15:55-07:00
Feature Requests - version 103
Mon Mar 10 03:15:55 -0700 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Add a web hook for pull requests</h3>
<p>Just a simple json <span class="caps">POST</span> to a <span class="caps">URL</span>, like the post-receive-hook. It would be useful for e.g: posting the request to a mailing list or automatically create a patch review.</p>
<h3>Edit active and not “current” revision on wiki</h3>
<p>When pressing “edit” on a wiki page, edit the viewed revision rather than the latest. This makes restoring old revisions easier, or using an old revision as base for new edits.</p>
<h3>Make it easier to make a navigatable wiki-page with anchors and link list</h3>
<p>Like I have done manually at <a href="https://github.com/dag/amazing/wikis/configuration/22">this page</a>.</p>
<h3>Attempt to match the commit Author to the github profile’s username, name, and email.</h3>
<p>Right now I own a project but my git author name is my full name spelled out, so it my github name, but not my github username. And it’s not showing me as author of my commits.</p>
<h3>Provide ability to add Google Analytics tracking code to repo home page</h3>
<p>Allow owners to analyze the viewership of their project by providing the ability to specify a snippet of <span class="caps">HTML</span>/JS for the google tracking code. If the snippet of JS is undesireable to be inserted directly into the page body you could instead embed this code on the site and embed just the user’s unique tracking code into that JS for them. Having visibility into who is viewing project is powerful.</p>
<p>Code looks like:</p>
<p>< script src=”https://www.google-analytics.com/urchin.js” type=”text/javascript”>
</ script>
< script type=”text/javascript”>
_uacct = “INSERT_UNIQUE_USER_TRACKING_ID_HERE”;
urchinTracker();
</ script></p>
<h3>Resend invitation</h3>
<p>Right now (2008-03-08), if you send an invitation out and it gets “lost,” there is no resend capability—and entering in the email address again gives you a message saying it can’t send another. Maybe this should be more friendly, and just resend?</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h3>Just a simple label that says “read-only” next to the public clone <span class="caps">URL</span></h3>
<p>I know there’s a note about this in the <span class="caps">FAQ</span>, but for those new to git, it could be helpful.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h3><del>Forgotten Password Link</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
pcapriotti
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-09T17:16:29-07:00
Feature Requests - version 102
Sun Mar 09 17:16:29 -0700 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Edit active and not “current” revision on wiki</h3>
<p>When pressing “edit” on a wiki page, edit the viewed revision rather than the latest. This makes restoring old revisions easier, or using an old revision as base for new edits.</p>
<h3>Make it easier to make a navigatable wiki-page with anchors and link list</h3>
<p>Like I have done manually at <a href="https://github.com/dag/amazing/wikis/configuration/22">this page</a>.</p>
<h3>Attempt to match the commit Author to the github profile’s username, name, and email.</h3>
<p>Right now I own a project but my git author name is my full name spelled out, so it my github name, but not my github username. And it’s not showing me as author of my commits.</p>
<h3>Provide ability to add Google Analytics tracking code to repo home page</h3>
<p>Allow owners to analyze the viewership of their project by providing the ability to specify a snippet of <span class="caps">HTML</span>/JS for the google tracking code. If the snippet of JS is undesireable to be inserted directly into the page body you could instead embed this code on the site and embed just the user’s unique tracking code into that JS for them. Having visibility into who is viewing project is powerful.</p>
<p>Code looks like:</p>
<p>< script src=”https://www.google-analytics.com/urchin.js” type=”text/javascript”>
</ script>
< script type=”text/javascript”>
_uacct = “INSERT_UNIQUE_USER_TRACKING_ID_HERE”;
urchinTracker();
</ script></p>
<h3>Resend invitation</h3>
<p>Right now (2008-03-08), if you send an invitation out and it gets “lost,” there is no resend capability—and entering in the email address again gives you a message saying it can’t send another. Maybe this should be more friendly, and just resend?</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h3>Just a simple label that says “read-only” next to the public clone <span class="caps">URL</span></h3>
<p>I know there’s a note about this in the <span class="caps">FAQ</span>, but for those new to git, it could be helpful.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h3><del>Forgotten Password Link</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
dag
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-09T15:58:32-07:00
Feature Requests - version 101
Sun Mar 09 15:58:32 -0700 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Make it easier to make a navigatable wiki-page with anchors and link list</h3>
<p>Like I have done manually at <a href="https://github.com/dag/amazing/wikis/configuration/22">this page</a>.</p>
<h3>Attempt to match the commit Author to the github profile’s username, name, and email.</h3>
<p>Right now I own a project but my git author name is my full name spelled out, so it my github name, but not my github username. And it’s not showing me as author of my commits.</p>
<h3>Provide ability to add Google Analytics tracking code to repo home page</h3>
<p>Allow owners to analyze the viewership of their project by providing the ability to specify a snippet of <span class="caps">HTML</span>/JS for the google tracking code. If the snippet of JS is undesireable to be inserted directly into the page body you could instead embed this code on the site and embed just the user’s unique tracking code into that JS for them. Having visibility into who is viewing project is powerful.</p>
<p>Code looks like:</p>
<p>< script src=”https://www.google-analytics.com/urchin.js” type=”text/javascript”>
</ script>
< script type=”text/javascript”>
_uacct = “INSERT_UNIQUE_USER_TRACKING_ID_HERE”;
urchinTracker();
</ script></p>
<h3>Resend invitation</h3>
<p>Right now (2008-03-08), if you send an invitation out and it gets “lost,” there is no resend capability—and entering in the email address again gives you a message saying it can’t send another. Maybe this should be more friendly, and just resend?</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h3>Just a simple label that says “read-only” next to the public clone <span class="caps">URL</span></h3>
<p>I know there’s a note about this in the <span class="caps">FAQ</span>, but for those new to git, it could be helpful.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h3><del>Forgotten Password Link</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
dag
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-09T15:57:58-07:00
Feature Requests - version 100
Sun Mar 09 15:57:58 -0700 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Make it easier to make a navigatable wiki-page with anchors and link list</h3>
<p>Like I have done manually at https://github.com/dag/amazing/wikis/configuration/22</p>
<h3>Attempt to match the commit Author to the github profile’s username, name, and email.</h3>
<p>Right now I own a project but my git author name is my full name spelled out, so it my github name, but not my github username. And it’s not showing me as author of my commits.</p>
<h3>Provide ability to add Google Analytics tracking code to repo home page</h3>
<p>Allow owners to analyze the viewership of their project by providing the ability to specify a snippet of <span class="caps">HTML</span>/JS for the google tracking code. If the snippet of JS is undesireable to be inserted directly into the page body you could instead embed this code on the site and embed just the user’s unique tracking code into that JS for them. Having visibility into who is viewing project is powerful.</p>
<p>Code looks like:</p>
<p>< script src=”https://www.google-analytics.com/urchin.js” type=”text/javascript”>
</ script>
< script type=”text/javascript”>
_uacct = “INSERT_UNIQUE_USER_TRACKING_ID_HERE”;
urchinTracker();
</ script></p>
<h3>Resend invitation</h3>
<p>Right now (2008-03-08), if you send an invitation out and it gets “lost,” there is no resend capability—and entering in the email address again gives you a message saying it can’t send another. Maybe this should be more friendly, and just resend?</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h3>Just a simple label that says “read-only” next to the public clone <span class="caps">URL</span></h3>
<p>I know there’s a note about this in the <span class="caps">FAQ</span>, but for those new to git, it could be helpful.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h3><del>Forgotten Password Link</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
dag
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-09T12:18:53-07:00
Feature Requests - version 99
Sun Mar 09 12:18:53 -0700 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Attempt to match the commit Author to the github profile’s username, name, and email.</h3>
<p>Right now I own a project but my git author name is my full name spelled out, so it my github name, but not my github username. And it’s not showing me as author of my commits.</p>
<h3>Provide ability to add Google Analytics tracking code to repo home page</h3>
<p>Allow owners to analyze the viewership of their project by providing the ability to specify a snippet of <span class="caps">HTML</span>/JS for the google tracking code. If the snippet of JS is undesireable to be inserted directly into the page body you could instead embed this code on the site and embed just the user’s unique tracking code into that JS for them. Having visibility into who is viewing project is powerful.</p>
<p>Code looks like:</p>
<p>< script src=”https://www.google-analytics.com/urchin.js” type=”text/javascript”>
</ script>
< script type=”text/javascript”>
_uacct = “INSERT_UNIQUE_USER_TRACKING_ID_HERE”;
urchinTracker();
</ script></p>
<h3>Resend invitation</h3>
<p>Right now (2008-03-08), if you send an invitation out and it gets “lost,” there is no resend capability—and entering in the email address again gives you a message saying it can’t send another. Maybe this should be more friendly, and just resend?</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h3>Just a simple label that says “read-only” next to the public clone <span class="caps">URL</span></h3>
<p>I know there’s a note about this in the <span class="caps">FAQ</span>, but for those new to git, it could be helpful.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h3><del>Forgotten Password Link</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
mdaines
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-09T11:20:57-07:00
Feature Requests - version 98
Sun Mar 09 11:20:57 -0700 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Attempt to match the commit Author to the github profile’s username, name, and email.</h3>
<p>Right now I own a project but my git author name is my full name spelled out, so it my github name, but not my github username. And it’s not showing me as author of my commits.</p>
<h3>Provide ability to add Google Analytics tracking code to repo home page</h3>
<p>Allow owners to analyze the viewership of their project by providing the ability to specify a snippet of <span class="caps">HTML</span>/JS for the google tracking code. If the snippet of JS is undesireable to be inserted directly into the page body you could instead embed this code on the site and embed just the user’s unique tracking code into that JS for them. Having visibility into who is viewing project is powerful.</p>
<p>Code looks like:</p>
<p>< script src=”https://www.google-analytics.com/urchin.js” type=”text/javascript”>
</ script>
< script type=”text/javascript”>
_uacct = “INSERT_UNIQUE_USER_TRACKING_ID_HERE”;
urchinTracker();
</ script></p>
<h3>Resend invitation</h3>
<p>Right now (2008-03-08), if you send an invitation out and it gets “lost,” there is no resend capability—and entering in the email address again gives you a message saying it can’t send another. Maybe this should be more friendly, and just resend?</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h3><del>Forgotten Password Link</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
robhudson
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-09T11:20:41-07:00
Feature Requests - version 97
Sun Mar 09 11:20:41 -0700 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Attempt to match the commit Author to the user profile’s username, name, and email.</h3>
<p>Right now I own a project but my git author name is my full name spelled out, so it my github name, but not my github username. And it’s not showing me as author of my commits.</p>
<h3>Provide ability to add Google Analytics tracking code to repo home page</h3>
<p>Allow owners to analyze the viewership of their project by providing the ability to specify a snippet of <span class="caps">HTML</span>/JS for the google tracking code. If the snippet of JS is undesireable to be inserted directly into the page body you could instead embed this code on the site and embed just the user’s unique tracking code into that JS for them. Having visibility into who is viewing project is powerful.</p>
<p>Code looks like:</p>
<p>< script src=”https://www.google-analytics.com/urchin.js” type=”text/javascript”>
</ script>
< script type=”text/javascript”>
_uacct = “INSERT_UNIQUE_USER_TRACKING_ID_HERE”;
urchinTracker();
</ script></p>
<h3>Resend invitation</h3>
<p>Right now (2008-03-08), if you send an invitation out and it gets “lost,” there is no resend capability—and entering in the email address again gives you a message saying it can’t send another. Maybe this should be more friendly, and just resend?</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h3><del>Forgotten Password Link</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
robhudson
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-09T11:20:28-07:00
Feature Requests - version 96
Sun Mar 09 11:20:28 -0700 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Attempt to match the commit Author to the user profile’s username, name, and email. Right now I own a project but my git author name is my full name spelled out, so it my github name, but not my github username. And it’s not showing me as author of my commits.</h3>
<h3>Provide ability to add Google Analytics tracking code to repo home page</h3>
<p>Allow owners to analyze the viewership of their project by providing the ability to specify a snippet of <span class="caps">HTML</span>/JS for the google tracking code. If the snippet of JS is undesireable to be inserted directly into the page body you could instead embed this code on the site and embed just the user’s unique tracking code into that JS for them. Having visibility into who is viewing project is powerful.</p>
<p>Code looks like:</p>
<p>< script src=”https://www.google-analytics.com/urchin.js” type=”text/javascript”>
</ script>
< script type=”text/javascript”>
_uacct = “INSERT_UNIQUE_USER_TRACKING_ID_HERE”;
urchinTracker();
</ script></p>
<h3>Resend invitation</h3>
<p>Right now (2008-03-08), if you send an invitation out and it gets “lost,” there is no resend capability—and entering in the email address again gives you a message saying it can’t send another. Maybe this should be more friendly, and just resend?</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h3><del>Forgotten Password Link</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
robhudson
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-09T11:11:44-07:00
Feature Requests - version 95
Sun Mar 09 11:11:44 -0700 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Provide ability to add Google Analytics tracking code to repo home page</h3>
<p>Allow owners to analyze the viewership of their project by providing the ability to specify a snippet of <span class="caps">HTML</span>/JS for the google tracking code. If the snippet of JS is undesireable to be inserted directly into the page body you could instead embed this code on the site and embed just the user’s unique tracking code into that JS for them. Having visibility into who is viewing project is powerful.</p>
<p>Code looks like:</p>
<p>< script src=”https://www.google-analytics.com/urchin.js” type=”text/javascript”>
</ script>
< script type=”text/javascript”>
_uacct = “INSERT_UNIQUE_USER_TRACKING_ID_HERE”;
urchinTracker();
</ script></p>
<h3>Resend invitation</h3>
<p>Right now (2008-03-08), if you send an invitation out and it gets “lost,” there is no resend capability—and entering in the email address again gives you a message saying it can’t send another. Maybe this should be more friendly, and just resend?</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h3><del>Forgotten Password Link</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
grempe
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-09T11:10:50-07:00
Feature Requests - version 94
Sun Mar 09 11:10:50 -0700 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Provide ability to add Google Analytics tracking code to repo home page</h3>
<p>Allow owners to analyze the viewership of their project by providing the ability to specify a snippet of <span class="caps">HTML</span>/JS for the google tracking code. If the snippet of JS is undesireable to be inserted directly into the page body you could instead embed this code on the site and embed just the user’s unique tracking code into that JS for them. Having visibility into who is viewing project is powerful.</p>
<p>Code looks like:</p>
<script src="https://www.google-analytics.com/urchin.js" type="text/javascript">
</script>
<script type="text/javascript">
_uacct = “INSERT_UNIQUE_USER_TRACKING_ID_HERE”;
urchinTracker();
</script>
<h3>Resend invitation</h3>
<p>Right now (2008-03-08), if you send an invitation out and it gets “lost,” there is no resend capability—and entering in the email address again gives you a message saying it can’t send another. Maybe this should be more friendly, and just resend?</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h3><del>Forgotten Password Link</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
grempe
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-08T21:02:00-08:00
Feature Requests - version 93
Sat Mar 08 21:02:00 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Resend invitation</h3>
<p>Right now (2008-03-08), if you send an invitation out and it gets “lost,” there is no resend capability—and entering in the email address again gives you a message saying it can’t send another. Maybe this should be more friendly, and just resend?</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h3><del>Forgotten Password Link</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
defunkt
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-08T17:01:13-08:00
Feature Requests - version 92
Sat Mar 08 17:01:13 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Resend invitation</h3>
<p>Right now (2008-03-08), if you send an invitation out and it gets “lost,” there is no resend capability—and entering in the email address again gives you a message saying it can’t send another. Maybe this should be more friendly, and just resend?</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
bruce
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-07T16:28:56-08:00
Feature Requests - version 91
Fri Mar 07 16:28:56 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>offer a link to the raw diff file</h3>
<p>GitHub has a hidden feature, you can see a diff in 2 formats: html and .diff</p>
<p>this <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146">commit</a> for instance has a nice default html view, but it also has a raw diff view: <a href="https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff">https://github.com/wycats/merb-more/commit/6dcdee33f172bc2229ec5eb01ddaadf988eab146.diff</a></p>
<p>It would be great to have a link to the raw diff when you look at the default view. (html)</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
mattetti
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-07T09:28:36-08:00
Feature Requests - version 90
Fri Mar 07 09:28:36 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Offer S3 repo backup</h3>
<p>A nightly backup to a user’s S3 bucket would be a great features for private repo owners.</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
mattetti
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-06T16:34:42-08:00
Feature Requests - version 89
Thu Mar 06 16:34:42 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>some way to search for repositories from your home dashboard besides going to the footer and clicking on “Repositories”</h3>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
sonian
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-06T10:35:13-08:00
Feature Requests - version 88
Thu Mar 06 10:35:13 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>List git tags in the commit log visualization</h3>
<p>So it’s obvious where in the history the tag has been put. Just like on repo.or.cz.</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
ruphy
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-06T04:49:18-08:00
Feature Requests - version 87
Thu Mar 06 04:49:18 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Show a stat with commits</h3>
<p>Allow an overview of commits just like git log—stat</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
frim
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-05T13:28:00-08:00
Feature Requests - version 86
Wed Mar 05 13:28:00 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.
Most corporate firewalls will disallow 9418/tcp, so this request would create a great deal more accessibility for repo cloning.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
mgrimes
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-05T11:33:09-08:00
Feature Requests - version 85
Wed Mar 05 11:33:09 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Preview changes to wiki pages</h3>
<p>I find myself spamming the history alot. :)</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
dag
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-05T08:24:52-08:00
Feature Requests - version 84
Wed Mar 05 08:24:52 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>This is perhaps the most limiting aspect of this site.</p>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
gregwebs
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-05T08:24:31-08:00
Feature Requests - version 83
Wed Mar 05 08:24:31 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories
This is perhaps the most limiting aspect of this site.</h3>
<ul>
<li>Search by description should already be done</li>
<li>Tagging could help</li>
<li>Search by <span class="caps">README</span></li>
</ul>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
gregwebs
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-05T08:21:23-08:00
Feature Requests - version 82
Wed Mar 05 08:21:23 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<p>A better way to do this is to always save wiki pages as html. Then you are not beholden to an individual markup, and it is easy to add a rich editor like the WYMeditor plugin for rails.</p>
<h3>Search for public repositories</h3>
<p>A search box might be nice. Search by name, description, tag, whatever.</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
gregwebs
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-04T16:50:08-08:00
Feature Requests - version 81
Tue Mar 04 16:50:08 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Better Locale support – or ‘Make the dates work for non-USAs’</h3>
<p><span class="caps">USA</span> dates looks wrong to me.</p>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<h3>Search for public repositories</h3>
<p>A search box might be nice. Search by name, description, tag, whatever.</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
rory
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-04T16:35:47-08:00
Feature Requests - version 80
Tue Mar 04 16:35:47 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>group access</h3>
<p>be able to specify user groups and grant everyone in that group access to a project</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<h3>Search for public repositories</h3>
<p>A search box might be nice. Search by name, description, tag, whatever.</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
BrianTheCoder
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-04T03:11:54-08:00
Feature Requests - version 79
Tue Mar 04 03:11:54 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<h3>Search for public repositories</h3>
<p>A search box might be nice. Search by name, description, tag, whatever.</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h3><del>Adding multiple keypairs for a repo</del></h3>
<p>Added.</p>
<h3><del>A repository should show list of users who are watching it.</del></h3>
<p>Added.</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
defunkt
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-03T16:08:10-08:00
Feature Requests - version 78
Mon Mar 03 16:08:10 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<h3>Search for public repositories</h3>
<p>A search box might be nice. Search by name, description, tag, whatever.</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>A repository should show list of users who are watching it.</h3>
<p>If this already exists I couldn’t find it, but it would be nice to know who is interested in my repositories without having to go back through the timeline of events.</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h3><del>Enable syntax highlighting for c++ files with a .cc extension</del></h3>
<p>Fixed.</p>
<h3><del>Zip/tar snapshot downloads</del>“</h3>
<p><a href="https://github.com/blog/12-tarball-downloads">https://github.com/blog/12-tarball-downloads</a></p>
<h3><del>At least some rough idea of payment plans</del></h3>
<p><a href="https://github.com/blog/11-github--free-for-open-source">https://github.com/blog/11-github—free-for-open-source</a></p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
defunkt
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-03T15:52:13-08:00
Feature Requests - version 77
Mon Mar 03 15:52:13 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<h3>-Enable syntax highlighting for c++ files with a .cc extension</h3>
<h3>Search for public repositories</h3>
<p>A search box might be nice. Search by name, description, tag, whatever.</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have .gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3>Zip/tar snapshot downloads</h3>
<p>The biggest thing holding me back from dropping cgit and moving over here… cgit’z zip downloads. It would rock to be able to link people to download zips, not ever user needs to go thru the buggery of making git work just so they can download. If you want examples, dig around my cgit at git.tekkub.net</p>
<h3>At least some rough idea of payment plans</h3>
<p>Just so I’m not wasting my time getting myself all cozy in the hub only to find out it kills my budget when it goes v1. Go on, post some ballpark figures. I double dare you!</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>A repository should show list of users who are watching it.</h3>
<p>If this already exists I couldn’t find it, but it would be nice to know who is interested in my repositories without having to go back through the timeline of events.</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/* or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
jamis
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-03T14:51:55-08:00
Feature Requests - version 76
Mon Mar 03 14:51:55 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<h3>-Enable syntax highlighting for c++ files with a .cc extension</h3>
<h3>Search for public repositories</h3>
<p>A search box might be nice. Search by name, description, tag, whatever.</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have <strong>.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3>Zip/tar snapshot downloads</h3>
<p>The biggest thing holding me back from dropping cgit and moving over here… cgit’z zip downloads. It would rock to be able to link people to download zips, not ever user needs to go thru the buggery of making git work just so they can download. If you want examples, dig around my cgit at git.tekkub.net</p>
<h3>At least some rough idea of payment plans</h3>
<p>Just so I’m not wasting my time getting myself all cozy in the hub only to find out it kills my budget when it goes v1. Go on, post some ballpark figures. I double dare you!</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>A repository should show list of users who are watching it.</h3>
<p>If this already exists I couldn’t find it, but it would be nice to know who is interested in my repositories without having to go back through the timeline of events.</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/</strong> or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.</p>
<h3>Shorter hash URLs in the UI</h3>
<p>The UI supports short hash URLs, but always displays long ones. Is it possible to only show the first six or eight characters in general? Makes emailing links a bit easier.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
dustin
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-03T14:35:28-08:00
Feature Requests - version 75
Mon Mar 03 14:35:28 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<h3>-Enable syntax highlighting for c++ files with a .cc extension</h3>
<h3>Search for public repositories</h3>
<p>A search box might be nice. Search by name, description, tag, whatever.</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have <strong>.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3>Zip/tar snapshot downloads</h3>
<p>The biggest thing holding me back from dropping cgit and moving over here… cgit’z zip downloads. It would rock to be able to link people to download zips, not ever user needs to go thru the buggery of making git work just so they can download. If you want examples, dig around my cgit at git.tekkub.net</p>
<h3>At least some rough idea of payment plans</h3>
<p>Just so I’m not wasting my time getting myself all cozy in the hub only to find out it kills my budget when it goes v1. Go on, post some ballpark figures. I double dare you!</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>A repository should show list of users who are watching it.</h3>
<p>If this already exists I couldn’t find it, but it would be nice to know who is interested in my repositories without having to go back through the timeline of events.</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/</strong> or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h3><span class="caps">HTTP</span> clone <span class="caps">URL</span></h3>
<p>A potential user pointed out that from behind his firewall, he couldn’t clone using the git protocol and asked for an http clone <span class="caps">URL</span>.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
dustin
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-03T06:49:08-08:00
Feature Requests - version 74
Mon Mar 03 06:49:08 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<h3>-Enable syntax highlighting for c++ files with a .cc extension</h3>
<h3>Search for public repositories</h3>
<p>A search box might be nice. Search by name, description, tag, whatever.</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have <strong>.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3>Zip/tar snapshot downloads</h3>
<p>The biggest thing holding me back from dropping cgit and moving over here… cgit’z zip downloads. It would rock to be able to link people to download zips, not ever user needs to go thru the buggery of making git work just so they can download. If you want examples, dig around my cgit at git.tekkub.net</p>
<h3>At least some rough idea of payment plans</h3>
<p>Just so I’m not wasting my time getting myself all cozy in the hub only to find out it kills my budget when it goes v1. Go on, post some ballpark figures. I double dare you!</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>A repository should show list of users who are watching it.</h3>
<p>If this already exists I couldn’t find it, but it would be nice to know who is interested in my repositories without having to go back through the timeline of events.</p>
<h3>Please support branch namespaces</h3>
<p>I frequently use branch names such as topic/</strong> or feature/* which have a common rebasing policy. Github’s web interface does not support this, though—the part before the slash gets stripped, and when I click on it, I get an error page.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
schutte
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-03T06:33:29-08:00
Feature Requests - version 73
Mon Mar 03 06:33:29 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<h3>-Enable syntax highlighting for c++ files with a .cc extension</h3>
<h3>Search for public repositories</h3>
<p>A search box might be nice. Search by name, description, tag, whatever.</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3>Zip/tar snapshot downloads</h3>
<p>The biggest thing holding me back from dropping cgit and moving over here… cgit’z zip downloads. It would rock to be able to link people to download zips, not ever user needs to go thru the buggery of making git work just so they can download. If you want examples, dig around my cgit at git.tekkub.net</p>
<h3>At least some rough idea of payment plans</h3>
<p>Just so I’m not wasting my time getting myself all cozy in the hub only to find out it kills my budget when it goes v1. Go on, post some ballpark figures. I double dare you!</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h3>A repository should show list of users who are watching it.</h3>
<p>If this already exists I couldn’t find it, but it would be nice to know who is interested in my repositories without having to go back through the timeline of events.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
seangeo
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-03T00:11:18-08:00
Feature Requests - version 72
Mon Mar 03 00:11:18 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<h3>-Enable syntax highlighting for c++ files with a .cc extension</h3>
<h3>Search for public repositories</h3>
<p>A search box might be nice. Search by name, description, tag, whatever.</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3>Zip/tar snapshot downloads</h3>
<p>The biggest thing holding me back from dropping cgit and moving over here… cgit’z zip downloads. It would rock to be able to link people to download zips, not ever user needs to go thru the buggery of making git work just so they can download. If you want examples, dig around my cgit at git.tekkub.net</p>
<h3>At least some rough idea of payment plans</h3>
<p>Just so I’m not wasting my time getting myself all cozy in the hub only to find out it kills my budget when it goes v1. Go on, post some ballpark figures. I double dare you!</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h3>Merging of repositories</h3>
<p>In my exuberance, I created a repo for a plugin for which I’m not the maintainer. Later on, the maintainer comes along and creates a new repo with the exact same name. I can’t easily make my repo part of his network without deleting and recreating it. I didn’t try this, but I don’t know if I can even push cleanly from my old repo to my newly created one given they didn’t exactly descend from the same repo (or is git smart about this?).</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
kamal
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-02T23:30:25-08:00
Feature Requests - version 71
Sun Mar 02 23:30:25 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>markdown or reStructuredText options for wiki editing</h3>
<p>reST is the de facto documentation markup for Python modules. Markdown is coincidentally (almost?) a subset thereof, and extremely popular. Thus the addition of either as formatting options to the wiki pages would be very welcome. I don’t know about the availability of a reST plugin for Rails, but Markdown certainly has to be out there.</p>
<h3>-Enable syntax highlighting for c++ files with a .cc extension</h3>
<h3>Search for public repositories</h3>
<p>A search box might be nice. Search by name, description, tag, whatever.</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3>Zip/tar snapshot downloads</h3>
<p>The biggest thing holding me back from dropping cgit and moving over here… cgit’z zip downloads. It would rock to be able to link people to download zips, not ever user needs to go thru the buggery of making git work just so they can download. If you want examples, dig around my cgit at git.tekkub.net</p>
<h3>At least some rough idea of payment plans</h3>
<p>Just so I’m not wasting my time getting myself all cozy in the hub only to find out it kills my budget when it goes v1. Go on, post some ballpark figures. I double dare you!</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
thedaniel
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-02T14:20:10-08:00
Feature Requests - version 70
Sun Mar 02 14:20:10 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>-Enable syntax highlighting for c++ files with a .cc extension</h3>
<h3>Search for public repositories</h3>
<p>A search box might be nice. Search by name, description, tag, whatever.</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3>Zip/tar snapshot downloads</h3>
<p>The biggest thing holding me back from dropping cgit and moving over here… cgit’z zip downloads. It would rock to be able to link people to download zips, not ever user needs to go thru the buggery of making git work just so they can download. If you want examples, dig around my cgit at git.tekkub.net</p>
<h3>At least some rough idea of payment plans</h3>
<p>Just so I’m not wasting my time getting myself all cozy in the hub only to find out it kills my budget when it goes v1. Go on, post some ballpark figures. I double dare you!</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h3>News Feed succinctness</h3>
<p>See <a href="https://skitch.com/drnic/8d7i/show-multiple-commits-as-just-one-commit-on-news-feed">example page</a></p>
<p>Some devs (e.g. me) are “commit happy” – but this cause cause pollution on the News Feed pages, thus pushing commits to other projects off the front page even though they might have also happened very recently. If several commits from one fork/developer were compressed onto a single news item, then more interesting news could be displayed on a single News Feed page.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
drnic
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-02T13:21:56-08:00
Feature Requests - version 69
Sun Mar 02 13:21:56 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>-Enable syntax highlighting for c++ files with a .cc extension</h3>
<h3>Search for public repositories</h3>
<p>A search box might be nice. Search by name, description, tag, whatever.</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3>Zip/tar snapshot downloads</h3>
<p>The biggest thing holding me back from dropping cgit and moving over here… cgit’z zip downloads. It would rock to be able to link people to download zips, not ever user needs to go thru the buggery of making git work just so they can download. If you want examples, dig around my cgit at git.tekkub.net</p>
<h3>At least some rough idea of payment plans</h3>
<p>Just so I’m not wasting my time getting myself all cozy in the hub only to find out it kills my budget when it goes v1. Go on, post some ballpark figures. I double dare you!</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h3>Bug tracking</h3>
<p>It would be great to track bugs/feature requests for a project and tie them to specific commits. If this exists somewhere already, I haven’t found it.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
foobarbazquux
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-01T19:00:37-08:00
Feature Requests - version 68
Sat Mar 01 19:00:37 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>-Enable syntax highlighting for c++ files with a .cc extension</h3>
<h3>Search for public repositories</h3>
<p>A search box might be nice. Search by name, description, tag, whatever.</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3>Zip/tar snapshot downloads</h3>
<p>The biggest thing holding me back from dropping cgit and moving over here… cgit’z zip downloads. It would rock to be able to link people to download zips, not ever user needs to go thru the buggery of making git work just so they can download. If you want examples, dig around my cgit at git.tekkub.net</p>
<h3>At least some rough idea of payment plans</h3>
<p>Just so I’m not wasting my time getting myself all cozy in the hub only to find out it kills my budget when it goes v1. Go on, post some ballpark figures. I double dare you!</p>
<h3><span class="caps">RSS</span> Feeds For New Repos</h3>
<p>The default repository page shows new projects coming up, but I’d like to be able to have that delivered to me automatically.</p>
<p>Alternatively, the news feed is quite useful, but contains <i>too much</i> stuff. If I could just select the types of news I wanted, that would be ideal.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
dustin
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-01T06:36:18-08:00
Feature Requests - version 67
Sat Mar 01 06:36:18 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>-Enable syntax highlighting for c++ files with a .cc extension</h3>
<h3>Search for public repositories</h3>
<p>A search box might be nice. Search by name, description, tag, whatever.</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3>Zip/tar snapshot downloads</h3>
<p>The biggest thing holding me back from dropping cgit and moving over here… cgit’z zip downloads. It would rock to be able to link people to download zips, not ever user needs to go thru the buggery of making git work just so they can download. If you want examples, dig around my cgit at git.tekkub.net</p>
<h3>At least some rough idea of payment plans</h3>
<p>Just so I’m not wasting my time getting myself all cozy in the hub only to find out it kills my budget when it goes v1. Go on, post some ballpark figures. I double dare you!</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
easytiger
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-01T06:35:52-08:00
Feature Requests - version 66
Sat Mar 01 06:35:52 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Search for public repositories</h3>
<p>A search box might be nice. Search by name, description, tag, whatever.</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3>Zip/tar snapshot downloads</h3>
<p>The biggest thing holding me back from dropping cgit and moving over here… cgit’z zip downloads. It would rock to be able to link people to download zips, not ever user needs to go thru the buggery of making git work just so they can download. If you want examples, dig around my cgit at git.tekkub.net</p>
<h3>At least some rough idea of payment plans</h3>
<p>Just so I’m not wasting my time getting myself all cozy in the hub only to find out it kills my budget when it goes v1. Go on, post some ballpark figures. I double dare you!</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
<h3>-Enable syntax highlighting for c++ files with a .cc extension</h3>
easytiger
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-03-01T02:39:54-08:00
Feature Requests - version 65
Sat Mar 01 02:39:54 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Search for public repositories</h3>
<p>A search box might be nice. Search by name, description, tag, whatever.</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3>Zip/tar snapshot downloads</h3>
<p>The biggest thing holding me back from dropping cgit and moving over here… cgit’z zip downloads. It would rock to be able to link people to download zips, not ever user needs to go thru the buggery of making git work just so they can download. If you want examples, dig around my cgit at git.tekkub.net</p>
<h3>At least some rough idea of payment plans</h3>
<p>Just so I’m not wasting my time getting myself all cozy in the hub only to find out it kills my budget when it goes v1. Go on, post some ballpark figures. I double dare you!</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p><del>When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</del></p>
<p>Added. – defunkt</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h3>Remove repositories</h3>
<p><del>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</del></p>
<p>Bug. Fixed. – defunkt</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
defunkt
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-28T01:11:11-08:00
Feature Requests - version 64
Thu Feb 28 01:11:11 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Search for public repositories</h3>
<p>A search box might be nice. Search by name, description, tag, whatever.</p>
<h3>(Small Thing) – href value of URLs</h3>
<p>- When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3>Zip/tar snapshot downloads</h3>
<p>The biggest thing holding me back from dropping cgit and moving over here… cgit’z zip downloads. It would rock to be able to link people to download zips, not ever user needs to go thru the buggery of making git work just so they can download. If you want examples, dig around my cgit at git.tekkub.net</p>
<h3>At least some rough idea of payment plans</h3>
<p>Just so I’m not wasting my time getting myself all cozy in the hub only to find out it kills my budget when it goes v1. Go on, post some ballpark figures. I double dare you!</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h3>User Aliases</h3>
<p><del>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</del></p>
<p>Done. Use the ‘account’ link in your user badge. – defunkt</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3><del>Be able to specify a link to the bug tracking page for a project</del></h3>
<h3><del>Be able to specify a link to the group forum/discussion page for a project</del></h3>
<p>We want to keep the ‘details’ box pretty simple. Use the wiki home page for this. – defunkt</p>
defunkt
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-27T17:11:31-08:00
Feature Requests - version 63
Wed Feb 27 17:11:31 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Search for public repositories</h3>
<p>A search box might be nice. Search by name, description, tag, whatever.</p>
<h3>(Small Thing) – href value of URLs</h3>
<p>- When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Multiple e-mails</h3>
<p>I, and many others I know, use an e-mail system where each site they sign up for has it’s own unique address. This allows us to instantly source and squash spam leakage. However, I much prefer to use my ‘real’ human e-mail address in my git commits. It’d be nice to be able to define extra e-mail addresses in preferences that will be recognized in commits as being from us.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3>Zip/tar snapshot downloads</h3>
<p>The biggest thing holding me back from dropping cgit and moving over here… cgit’z zip downloads. It would rock to be able to link people to download zips, not ever user needs to go thru the buggery of making git work just so they can download. If you want examples, dig around my cgit at git.tekkub.net</p>
<h3>At least some rough idea of payment plans</h3>
<p>Just so I’m not wasting my time getting myself all cozy in the hub only to find out it kills my budget when it goes v1. Go on, post some ballpark figures. I double dare you!</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
francois
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-27T03:26:09-08:00
Feature Requests - version 62
Wed Feb 27 03:26:09 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>(Small Thing) – href value of URLs</h3>
<p>- When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Multiple e-mails</h3>
<p>I, and many others I know, use an e-mail system where each site they sign up for has it’s own unique address. This allows us to instantly source and squash spam leakage. However, I much prefer to use my ‘real’ human e-mail address in my git commits. It’d be nice to be able to define extra e-mail addresses in preferences that will be recognized in commits as being from us.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3>Zip/tar snapshot downloads</h3>
<p>The biggest thing holding me back from dropping cgit and moving over here… cgit’z zip downloads. It would rock to be able to link people to download zips, not ever user needs to go thru the buggery of making git work just so they can download. If you want examples, dig around my cgit at git.tekkub.net</p>
<h3>At least some rough idea of payment plans</h3>
<p>Just so I’m not wasting my time getting myself all cozy in the hub only to find out it kills my budget when it goes v1. Go on, post some ballpark figures. I double dare you!</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
leemhenson
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-26T23:30:55-08:00
Feature Requests - version 61
Tue Feb 26 23:30:55 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>(Small Thing) – href value of URLs</h3>
<p>- When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Multiple e-mails</h3>
<p>I, and many others I know, use an e-mail system where each site they sign up for has it’s own unique address. This allows us to instantly source and squash spam leakage. However, I much prefer to use my ‘real’ human e-mail address in my git commits. It’d be nice to be able to define extra e-mail addresses in preferences that will be recognized in commits as being from us.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3>Zip/tar snapshot downloads</h3>
<p>The biggest thing holding me back from dropping cgit and moving over here… cgit’z zip downloads. It would rock to be able to link people to download zips, not ever user needs to go thru the buggery of making git work just so they can download. If you want examples, dig around my cgit at git.tekkub.net</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
jdhuntington
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-26T23:30:23-08:00
Feature Requests - version 60
Tue Feb 26 23:30:23 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Multiple e-mails</h3>
<p>I, and many others I know, use an e-mail system where each site they sign up for has it’s own unique address. This allows us to instantly source and squash spam leakage. However, I much prefer to use my ‘real’ human e-mail address in my git commits. It’d be nice to be able to define extra e-mail addresses in preferences that will be recognized in commits as being from us.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3>Zip/tar snapshot downloads</h3>
<p>The biggest thing holding me back from dropping cgit and moving over here… cgit’z zip downloads. It would rock to be able to link people to download zips, not ever user needs to go thru the buggery of making git work just so they can download. If you want examples, dig around my cgit at git.tekkub.net</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
<h3>(Small Thing) – href value of URLs</h3>
<p>- When I want to do local work on my local system, my natural instinct is to right click on the ‘Public clone <span class="caps">URL</span>’, select ‘copy link location’ (safari), then paste it into my terminal window. Since this link is actually an anchor to a name with a javascript action, it does cause a bit of frustration every time it happens. Thanks!</p>
jdhuntington
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-26T19:35:08-08:00
Feature Requests - version 59
Tue Feb 26 19:35:08 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Multiple e-mails</h3>
<p>I, and many others I know, use an e-mail system where each site they sign up for has it’s own unique address. This allows us to instantly source and squash spam leakage. However, I much prefer to use my ‘real’ human e-mail address in my git commits. It’d be nice to be able to define extra e-mail addresses in preferences that will be recognized in commits as being from us.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h3>Zip/tar snapshot downloads</h3>
<p>The biggest thing holding me back from dropping cgit and moving over here… cgit’z zip downloads. It would rock to be able to link people to download zips, not ever user needs to go thru the buggery of making git work just so they can download. If you want examples, dig around my cgit at git.tekkub.net</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
tekkub
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-26T12:10:00-08:00
Feature Requests - version 58
Tue Feb 26 12:10:00 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Multiple e-mails</h3>
<p>I, and many others I know, use an e-mail system where each site they sign up for has it’s own unique address. This allows us to instantly source and squash spam leakage. However, I much prefer to use my ‘real’ human e-mail address in my git commits. It’d be nice to be able to define extra e-mail addresses in preferences that will be recognized in commits as being from us.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h3>.diff URLs for branches</h3>
<p>Okay I was about to submit this as a request but started playing and figured out that it was already partially supported. You can get a diff for any commit by tacking ’.diff’ onto the end of the commit <span class="caps">URL</span>:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c755945649fa70d53ffd171c2c74a53a21220e8f.diff</p>
<p>You can also shorten the hash, which rocks:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594.diff</p>
<p>Oh, and huge kudos for actually implementing <span class="caps">HTTP</span> content negotiation:</p>
<pre>
$ curl --header 'Accept: text/plain' https://github.com/rtomayko/nginx-port-upstream-fair/commit/c75594
</pre>
<p>That’s so amazingly beautiful.</p>
<p>I’d like to have the same kind of support for branches. The idea being that requesting something like:</p>
<p>https://github.com/rtomayko/nginx-port-upstream-fair/tree/upstream_fair.diff</p>
<p>Would give me a patch for all changes made on the “upstream_fair” branch. Unfortunately, I don’t know how to programatically determine the upstream for a branch. I generate diffs like this with git as follows:</p>
<pre>
git checkout upstream_fair
git diff master...
</pre>
<p>The ”...” form figures out the common base between master and <span class="caps">HEAD</span> on the current branch. But I don’t know if its possible to determine that the branch was created from “master”.</p>
<p>Anyway, this would be great for attach-patch-to-email type situations because you could just link to your branch’s diff.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
rtomayko
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-26T08:20:12-08:00
Feature Requests - version 57
Tue Feb 26 08:20:12 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Multiple e-mails</h3>
<p>I, and many others I know, use an e-mail system where each site they sign up for has it’s own unique address. This allows us to instantly source and squash spam leakage. However, I much prefer to use my ‘real’ human e-mail address in my git commits. It’d be nice to be able to define extra e-mail addresses in preferences that will be recognized in commits as being from us.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h3>Network page</h3>
<ul>
<li>Add the date of the most recent commits, to see what is ancient and what I may want to consider pulling from</li>
</ul>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
rsanheim
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-25T17:50:42-08:00
Feature Requests - version 56
Mon Feb 25 17:50:42 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Repo Avatars</h3>
<p>It would be nice to be able to supply per-repo avatars,
so that it’s easy to tell various repos apart at a glance
from the news feed, /repositories, and so forth.</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Multiple e-mails</h3>
<p>I, and many others I know, use an e-mail system where each site they sign up for has it’s own unique address. This allows us to instantly source and squash spam leakage. However, I much prefer to use my ‘real’ human e-mail address in my git commits. It’d be nice to be able to define extra e-mail addresses in preferences that will be recognized in commits as being from us.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
nex3
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-25T14:43:05-08:00
Feature Requests - version 55
Mon Feb 25 14:43:05 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Multiple e-mails</h3>
<p>I, and many others I know, use an e-mail system where each site they sign up for has it’s own unique address. This allows us to instantly source and squash spam leakage. However, I much prefer to use my ‘real’ human e-mail address in my git commits. It’d be nice to be able to define extra e-mail addresses in preferences that will be recognized in commits as being from us.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h3>Allow user to specify homepage(s) in account page and link to them using rel=”me”</h3>
<p>That way <span class="caps">XFN</span> parsers can pay attention to our repositories! Maybe other microformats too?</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
tommorris
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-25T13:32:32-08:00
Feature Requests - version 54
Mon Feb 25 13:32:32 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Multiple e-mails</h3>
<p>I, and many others I know, use an e-mail system where each site they sign up for has it’s own unique address. This allows us to instantly source and squash spam leakage. However, I much prefer to use my ‘real’ human e-mail address in my git commits. It’d be nice to be able to define extra e-mail addresses in preferences that will be recognized in commits as being from us.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h3>Require forks to specify a reason for the fork that displays in search results</h3>
<p>For instance the following project: https://github.com/repositories/search?q=attachment_fu … It would be nice to be able to tell more easily which one I want to use or follow w/o having to read the docs. Forkers might also want to specify whether their fork is intended to be used or if they have a good relationship with an upstream maintainer.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
mmmurf
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-25T09:10:12-08:00
Feature Requests - version 53
Mon Feb 25 09:10:12 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Multiple e-mails</h3>
<p>I, and many others I know, use an e-mail system where each site they sign up for has it’s own unique address. This allows us to instantly source and squash spam leakage. However, I much prefer to use my ‘real’ human e-mail address in my git commits. It’d be nice to be able to define extra e-mail addresses in preferences that will be recognized in commits as being from us.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h2>Rejected</h2>
<h3>Create a new git repository from an svn repository</h3>
<p><del>Would be nice to be able to import an svn repository directly into github.</del></p>
<p>This is easier to do locally and then push to github. Check out the <a href="https://github.com/guides/import-from-subversion">guide</a></p>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
mojombo
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-25T05:53:52-08:00
Feature Requests - version 52
Mon Feb 25 05:53:52 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Multiple e-mails</h3>
<p>I, and many others I know, use an e-mail system where each site they sign up for has it’s own unique address. This allows us to instantly source and squash spam leakage. However, I much prefer to use my ‘real’ human e-mail address in my git commits. It’d be nice to be able to define extra e-mail addresses in preferences that will be recognized in commits as being from us.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Create a new git repository from an svn repository</h3>
<p>Would be nice to be able to import an svn repository directly into github.</p>
<h3>Separate forked repositories from other in user page</h3>
<p>Well, that’s pretty descriptive, isn’t it?</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h2>Rejected</h2>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
sr
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-25T02:17:05-08:00
Feature Requests - version 51
Mon Feb 25 02:17:05 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>Multiple e-mails</h3>
<p>I, and many others I know, use an e-mail system where each site they sign up for has it’s own unique address. This allows us to instantly source and squash spam leakage. However, I much prefer to use my ‘real’ human e-mail address in my git commits. It’d be nice to be able to define extra e-mail addresses in preferences that will be recognized in commits as being from us.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h3>Create a new git repository from an svn repository</h3>
<p>Would be nice to be able to import an svn repository directly into github.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h2>Rejected</h2>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
marten
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-24T19:35:07-08:00
Feature Requests - version 50
Sun Feb 24 19:35:07 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>multiple e-mails</h3>
<p>I, and many others I know, use an e-mail system where each site they sign up for has it’s own unique address. This allows us to instantly source and squash spam leakage. However, I much prefer to use my ‘real’ human e-mail address in my git commits. It’d be nice to be able to define extra e-mail addresses in preferences that will be recognized in commits as being from us.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h2>Accepted</h2>
<h3>Access over port 80 or 443</h3>
<p><del>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</del></p>
<p>There is now <span class="caps">SSL</span> for all private repos and user specific areas. – mojombo</p>
<h2>Rejected</h2>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
mojombo
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-24T19:32:29-08:00
Feature Requests - version 49
Sun Feb 24 19:32:29 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>multiple e-mails</h3>
<p>I, and many others I know, use an e-mail system where each site they sign up for has it’s own unique address. This allows us to instantly source and squash spam leakage. However, I much prefer to use my ‘real’ human e-mail address in my git commits. It’d be nice to be able to define extra e-mail addresses in preferences that will be recognized in commits as being from us.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h2>Accepted</h2>
<p>...</p>
<h2>Rejected</h2>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
mojombo
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-24T19:31:30-08:00
Feature Requests - version 48
Sun Feb 24 19:31:30 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>multiple e-mails</h3>
<p>I, and many others I know, use an e-mail system where each site they sign up for has it’s own unique address. This allows us to instantly source and squash spam leakage. However, I much prefer to use my ‘real’ human e-mail address in my git commits. It’d be nice to be able to define extra e-mail addresses in preferences that will be recognized in commits as being from us.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
<h2>Decisions</h2>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p><del>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</del></p>
<p>We won’t be supporting full textile or markdown for commits, but we may have some very simple formatting support later on. – mojombo</p>
mojombo
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-24T11:36:41-08:00
Feature Requests - version 47
Sun Feb 24 11:36:41 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Open Repo</h3>
<p>I’d like to have the option to allow anyone to push to my repo, like git-daemon’s “receivepack = true” option.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>multiple e-mails</h3>
<p>I, and many others I know, use an e-mail system where each site they sign up for has it’s own unique address. This allows us to instantly source and squash spam leakage. However, I much prefer to use my ‘real’ human e-mail address in my git commits. It’d be nice to be able to define extra e-mail addresses in preferences that will be recognized in commits as being from us.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
nex3
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-23T23:22:18-08:00
Feature Requests - version 46
Sat Feb 23 23:22:18 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>multiple e-mails</h3>
<p>I, and many others I know, use an e-mail system where each site they sign up for has it’s own unique address. This allows us to instantly source and squash spam leakage. However, I much prefer to use my ‘real’ human e-mail address in my git commits. It’d be nice to be able to define extra e-mail addresses in preferences that will be recognized in commits as being from us.</p>
<h3>Lighthouse integration</h3>
<p>The front page of github, when not logged in, advertises Lighthouse integration. However I can’t find any hint of this once logged in. Is this implemented? If so, there at least needs to be a guide about it.</p>
kballard
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-23T22:42:08-08:00
Feature Requests - version 45
Sat Feb 23 22:42:08 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
<h3>multiple e-mails</h3>
<p>I, and many others I know, use an e-mail system where each site they sign up for has it’s own unique address. This allows us to instantly source and squash spam leakage. However, I much prefer to use my ‘real’ human e-mail address in my git commits. It’d be nice to be able to define extra e-mail addresses in preferences that will be recognized in commits as being from us.</p>
elliottcable
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-23T13:39:24-08:00
Feature Requests - version 44
Sat Feb 23 13:39:24 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
<h3>Sort tags by date</h3>
<p>If one uses annotated tags (like they should) the tag gets a timestamp. It would seem more logical to sort the “All Tags” dropdown such that the newest tag is at the top, non-annotated tags could be sorted with the current alpha-sort after any annotated ones.</p>
tekkub
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-22T00:13:22-08:00
Feature Requests - version 43
Fri Feb 22 00:13:22 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3>Read-only Subversion Mirror</h3>
<p><del>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.</del>
<del>+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</del></p>
<p>Not going to happen. – defunkt</p>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
defunkt
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-21T23:33:40-08:00
Feature Requests - version 42
Thu Feb 21 23:33:40 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>Forgotten Password Link</h3>
<p>It would be nice to have a little thing that could send an email to your account to reset your password if its forgotten. I know of one person who is currently locked out of his account because of it.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><del><span class="caps">RSS</span> feeds for commits on branches</del> (or across a whole repo)</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
<h3>tags for public projects</h3>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3><span class="caps">RSS</span> feeds</h3>
<ul>
<li><del>for the help guides so we can be notified of helpful awesomeness</del></li>
</ul>
<h3>Read-only Subversion Mirror</h3>
<p>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.
+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</p>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
jmhodges
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-21T15:34:08-08:00
Feature Requests - version 41
Thu Feb 21 15:34:08 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><del><span class="caps">RSS</span> feeds for commits on branches</del> (or across a whole repo)</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
<h3>tags for public projects</h3>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3><span class="caps">RSS</span> feeds</h3>
<ul>
<li><del>for the help guides so we can be notified of helpful awesomeness</del></li>
</ul>
<h3>Read-only Subversion Mirror</h3>
<p>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.
+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</p>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
ctennis
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-21T15:34:07-08:00
Feature Requests - version 40
Thu Feb 21 15:34:07 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><del><span class="caps">RSS</span> feeds for commits on branches</del> (or across a whole repo)</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
<h3>tags for public projects</h3>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3><span class="caps">RSS</span> feeds</h3>
<ul>
<li><del>for the help guides so we can be notified of helpful awesomeness</del></li>
</ul>
<h3>Read-only Subversion Mirror</h3>
<p>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.
+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</p>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
<h3>Adding multiple keypairs for a repo</h3>
<p>Having the ability to add new public keys to a repo to allow the user holding that key to read or read/write to the repo, without necessarily having to give them an actual account. This is handy, for instance, if you have deployment machines that need to pull down repo changes, but aren’t tied to any individual user.</p>
ctennis
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-21T11:22:39-08:00
Feature Requests - version 39
Thu Feb 21 11:22:39 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><del><span class="caps">RSS</span> feeds for commits on branches</del> (or across a whole repo)</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
<h3>tags for public projects</h3>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3><span class="caps">RSS</span> feeds</h3>
<ul>
<li><del>for the help guides so we can be notified of helpful awesomeness</del></li>
</ul>
<h3>Read-only Subversion Mirror</h3>
<p>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.
+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</p>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
daikini
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-21T09:07:02-08:00
Feature Requests - version 38
Thu Feb 21 09:07:02 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><del><span class="caps">RSS</span> feeds for commits on branches</del> (or across a whole repo)</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
<h3>tags for public projects</h3>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3><span class="caps">RSS</span> feeds</h3>
<ul>
<li>for the help guides so we can be notified of helpful awesomeness</li>
</ul>
<h3>Read-only Subversion Mirror</h3>
<p>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin.
+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</p>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
sd
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-21T09:06:25-08:00
Feature Requests - version 37
Thu Feb 21 09:06:25 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><del><span class="caps">RSS</span> feeds for commits on branches</del> (or across a whole repo)</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
<h3>tags for public projects</h3>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3><span class="caps">RSS</span> feeds</h3>
<ul>
<li>for the help guides so we can be notified of helpful awesomeness</li>
</ul>
<h3>Read-only Subversion Mirror</h3>
<p>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin
+1 on this. Even better if you can specify which branch to mirror (i.e. the “released” branch)</p>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
<h3>Syntax coloring on wiki pages</h3>
<p>Use certain tags or a textile-ish markup to delimit source code fragments in a wiki page and specify which language to use.</p>
sd
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-21T05:12:59-08:00
Feature Requests - version 36
Thu Feb 21 05:12:59 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><del><span class="caps">RSS</span> feeds for commits on branches</del> (or across a whole repo)</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
<h3>tags for public projects</h3>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3><span class="caps">RSS</span> feeds</h3>
<ul>
<li>for the help guides so we can be notified of helpful awesomeness</li>
</ul>
<h3>Read-only Subversion Mirror</h3>
<p>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin</p>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</p>
<h3>Handle more file formats</h3>
<p>It would be nice if install.rdf could be displayed/diffed just like xml, and init.sh as a text file.</p>
anotherjesse
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-19T14:47:21-08:00
Feature Requests - version 35
Tue Feb 19 14:47:21 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><del><span class="caps">RSS</span> feeds for commits on branches</del> (or across a whole repo)</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
<h3>tags for public projects</h3>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3><span class="caps">RSS</span> feeds</h3>
<ul>
<li>for the help guides so we can be notified of helpful awesomeness</li>
</ul>
<h3>Read-only Subversion Mirror</h3>
<p>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin</p>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
<h3>Apply markdown or textile formatting to commit messages</h3>
<p>This is probably controversial, since there isn’t much of a precedent for doing this and it may mangle some messages, but it’d be nice I think. Especially for things like bulleted lists. Maybe a user-specific preference to have all their commit messages formatted as [None|Markdown|Textile]?</p>
willcodeforfoo
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-18T12:39:54-08:00
Feature Requests - version 34
Mon Feb 18 12:39:54 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><del><span class="caps">RSS</span> feeds for commits on branches</del> (or across a whole repo)</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
<h3>tags for public projects</h3>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3><span class="caps">RSS</span> feeds</h3>
<ul>
<li>for the help guides so we can be notified of helpful awesomeness</li>
</ul>
<h3>Read-only Subversion Mirror</h3>
<p>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin</p>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can discuss a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
grempe
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-18T12:38:11-08:00
Feature Requests - version 33
Mon Feb 18 12:38:11 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><del><span class="caps">RSS</span> feeds for commits on branches</del> (or across a whole repo)</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
<h3>tags for public projects</h3>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3><span class="caps">RSS</span> feeds</h3>
<ul>
<li>for the help guides so we can be notified of helpful awesomeness</li>
</ul>
<h3>Read-only Subversion Mirror</h3>
<p>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin</p>
<h3>Be able to specify a link to the bug tracking page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Be able to specify a link to the group forum/discussion page for a project</h3>
<p>So people can jump right to the page where they can log issues with a project.</p>
<h3>Provide raw http view of project and its files so ’./script/plugin install’ will work to install latest code from master branch.</h3>
<p>Github could make the job of publishing a new version of a plugin as simple as a ‘git push’.</p>
<h3>Provide an index of .gem files so ‘gem install foobar’ would work if Github were registered as a gem source.</h3>
<p>If a developer is managing a ruby gem source in github, and they have *.gem files in the pkg dir of their repos, have github make those available for gem download and installation. Alternatively, have a gem definition page where users could define either the dir that contains gems in their repos, or specific files that they want to be published as gems. Doing this would make rubyforge obsolete and github the master of the universe.</p>
grempe
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-17T20:02:30-08:00
Feature Requests - version 32
Sun Feb 17 20:02:30 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><del><span class="caps">RSS</span> feeds for commits on branches</del> (or across a whole repo)</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
<h3>tags for public projects</h3>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3><span class="caps">RSS</span> feeds</h3>
<ul>
<li>for the help guides so we can be notified of helpful awesomeness</li>
</ul>
<h3>Read-only Subversion Mirror</h3>
<p>For people still on subversion, <span class="caps">IIRC</span> Rails core refused to add git support to script/plugin</p>
kamal
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-15T15:01:24-08:00
Feature Requests - version 31
Fri Feb 15 15:01:24 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<p>Need help? Try #github in irc.freenode.net</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><del><span class="caps">RSS</span> feeds for commits on branches</del> (or across a whole repo)</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
<h3>tags for public projects</h3>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3><span class="caps">RSS</span> feeds</h3>
<ul>
<li>for the help guides so we can be notified of helpful awesomeness</li>
</ul>
defunkt
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-14T19:12:16-08:00
Feature Requests - version 30
Thu Feb 14 19:12:16 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><del><span class="caps">RSS</span> feeds for commits on branches</del> (or across a whole repo)</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
<h3>tags for public projects</h3>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3><span class="caps">RSS</span> feeds</h3>
<ul>
<li>for the help guides so we can be notified of helpful awesomeness</li>
</ul>
mojombo
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-14T10:33:17-08:00
Feature Requests - version 29
Thu Feb 14 10:33:17 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><del><span class="caps">RSS</span> feeds for commits on branches</del> (or across a whole repo)</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
<h3>tags for public projects</h3>
<h3><del>Ability to make a Private project Public, and vice versa</del></h3>
<p>nm, found it! ;)</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
<h3><span class="caps">RSS</span> feeds</h3>
<ul>
<li>for the help guides so we can be notified of helpful awesomeness</li>
</ul>
daikini
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-14T00:38:06-08:00
Feature Requests - version 28
Thu Feb 14 00:38:06 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><del><span class="caps">RSS</span> feeds for commits on branches</del> (or across a whole repo)</li>
<li>Network display to show most recent commit on any branch (e.g. https://github.com/drnic/ruby-on-rails-tmbundle/network)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
<h3>tags for public projects</h3>
<h3><del>Ability to make a Private project Public, and vice versa</del></h3>
<p>nm, found it! ;)</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
drnic
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-13T22:22:07-08:00
Feature Requests - version 27
Wed Feb 13 22:22:07 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><del><span class="caps">RSS</span> feeds for commits on branches</del> (or across a whole repo)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
<h3>tags for public projects</h3>
<h3><del>Ability to make a Private project Public, and vice versa</del></h3>
<p>nm, found it! ;)</p>
<h3>Categories of Repos</h3>
<ul>
<li>A one-click button to find porn related projects</li>
</ul>
drnic
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-13T18:43:37-08:00
Feature Requests - version 26
Wed Feb 13 18:43:37 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><del><span class="caps">RSS</span> feeds for commits on branches</del> (or across a whole repo)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
<h3>tags for public projects</h3>
<h3><del>Ability to make a Private project Public, and vice versa</del></h3>
<p>nm, found it! ;)</p>
cheapRoc
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-13T18:42:12-08:00
Feature Requests - version 25
Wed Feb 13 18:42:12 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><del><span class="caps">RSS</span> feeds for commits on branches</del> (or across a whole repo)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
<h3>tags for public projects</h3>
<h3>Ability to make a Private project Public, and vice versa</h3>
cheapRoc
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-13T16:04:46-08:00
Feature Requests - version 24
Wed Feb 13 16:04:46 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><del><span class="caps">RSS</span> feeds for commits on branches</del> (or across a whole repo)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
<h3>tags for public projects</h3>
defunkt
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-13T04:52:43-08:00
Feature Requests - version 23
Wed Feb 13 04:52:43 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><span class="caps">RSS</span> feeds for commits on branches (or across a whole repo)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
<h3>tags for public projects</h3>
deimos1986
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-13T03:31:38-08:00
Feature Requests - version 22
Wed Feb 13 03:31:38 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><span class="caps">RSS</span> feeds for commits on branches (or across a whole repo)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository that you haven’t yet pushed to, other than by hacking the <span class="caps">URL</span>.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
henrik
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-13T02:58:16-08:00
Feature Requests - version 21
Wed Feb 13 02:58:16 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><span class="caps">RSS</span> feeds for commits on branches (or across a whole repo)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository.</p>
<h3>Lighthouse and campfire integration</h3>
<p>Does this currently exist? If so some docs would be nice :)</p>
mloughran
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-13T02:09:48-08:00
Feature Requests - version 20
Wed Feb 13 02:09:48 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><span class="caps">RSS</span> feeds for commits on branches (or across a whole repo)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug</h3>
<p>So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</p>
<h3>Remove repositories</h3>
<p>Seems you can’t currently remove a repository.</p>
henrik
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-13T02:07:46-08:00
Feature Requests - version 19
Wed Feb 13 02:07:46 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><span class="caps">RSS</span> feeds for commits on branches (or across a whole repo)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
<h3>Set your own repository slug
So a project named “Foo.com Bar” could be “bar.git”, not “foo-com-bar.git”.</h3>
henrik
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-13T02:00:05-08:00
Feature Requests - version 18
Wed Feb 13 02:00:05 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><span class="caps">RSS</span> feeds for commits on branches (or across a whole repo)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects</h3>
<p>by username and title</p>
deimos1986
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-13T01:59:32-08:00
Feature Requests - version 17
Wed Feb 13 01:59:32 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><span class="caps">RSS</span> feeds for commits on branches (or across a whole repo)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
<h3>Search projects
by username and title</h3>
deimos1986
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-12T22:17:49-08:00
Feature Requests - version 16
Tue Feb 12 22:17:49 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><span class="caps">RSS</span> feeds for commits on branches (or across a whole repo)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3>Additional “syntax highlighting” support</h3>
<p>Elisp would be fantasmic.</p>
wfarr
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-12T22:06:15-08:00
Feature Requests - version 15
Tue Feb 12 22:06:15 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><span class="caps">RSS</span> feeds for commits on branches (or across a whole repo)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
<h3><span class="caps">CSS</span>-driven “syntax highlighting” for files based on matching the file extension/shebang</h3>
wfarr
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-12T14:59:10-08:00
Feature Requests - version 14
Tue Feb 12 14:59:10 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><span class="caps">RSS</span> feeds for commits on branches (or across a whole repo)</li>
</ul>
<h3>‘What next?’ post-fork</h3>
<p>Show something when I fork a repo explaining how to pull changes from the parent repo.</p>
defunkt
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-10T20:24:21-08:00
Feature Requests - version 13
Sun Feb 10 20:24:21 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
<h3>Branches are 1st class citizens</h3>
<ul>
<li>Statistics/graph of branches, not just ‘master’ on https://github.com/username page</li>
<li><span class="caps">RSS</span> feeds for commits on branches (or across a whole repo)</li>
</ul>
drnic
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-08T11:12:58-08:00
Feature Requests - version 12
Fri Feb 08 11:12:58 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over port 80 or 443</h3>
<p>Probably with <span class="caps">SSL</span> over 443, if possible. For those of us in corporate environments!</p>
tpitale
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-08T11:12:19-08:00
Feature Requests - version 11
Fri Feb 08 11:12:19 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
<h3>Access over 80/443</h3>
<p>For those of us in corporate environments!</p>
tpitale
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-06T13:01:30-08:00
Feature Requests - version 10
Wed Feb 06 13:01:30 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
<h3>Change username/email address and cancel account</h3>
<p>Straight-away I needed to change my username/email address, because I’m dumb, but can’t. Since I hadn’t used it yet, I decided to cancel the account and create a new one, but can’t do that either yet. :)</p>
sevenwire
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-06T10:33:49-08:00
Feature Requests - version 9
Wed Feb 06 10:33:49 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p><del>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</del></p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
schacon
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-03T14:38:54-08:00
Feature Requests - version 8
Sun Feb 03 14:38:54 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>OpenID</h3>
<p>OpenID authentication would be nice.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
josh
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-02T12:41:51-08:00
Feature Requests - version 7
Sat Feb 02 12:41:51 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>Little Things</h3>
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul>
defunkt
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-02T12:41:41-08:00
Feature Requests - version 6
Sat Feb 02 12:41:41 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages</h3>
<p>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects.</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</p>
<h3>Little Things
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul></h3>
defunkt
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-02T12:41:19-08:00
Feature Requests - version 5
Sat Feb 02 12:41:19 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<h3>Project Pages
I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</h3>
<h3>Cloning Stats
It would be pretty cool to see how many people are cloning our projects.</h3>
<h3>User Aliases
I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user.</h3>
<h3>Little Things
<ul>
<li><del>Click on your username/pic to go back to your home page</del></li>
</ul></h3>
defunkt
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-02-02T12:40:29-08:00
Feature Requests - version 4
Sat Feb 02 12:40:29 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I’m putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I’m sure they have to add them.</p>
<ul>
<li><strong>Project Pages</strong>: I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone’s blogs.</li>
</ul>
<ul>
<li><strong>Cloning Stats</strong>: It would be pretty cool to see how many people are cloning our projects.</li>
</ul>
<ul>
<li><strong>User Aliases</strong>: I have a couple of email addresses that I use or have used in the past – it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user</li>
</ul>
defunkt
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-01-31T10:48:45-08:00
Feature Requests - version 3
Thu Jan 31 10:48:45 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I'm putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I'm sure they have to add them.</p>
<h3>Project Pages</h3>
<p>I would love to see a page for the project that lists out all the users that have cloned it. Maybe this is not in keeping with the philosophy, but it would be neat to see the community around projects without having to go to everyone's blogs.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past - it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user</p>
<h3>Little Things</h3>
<ul>
<li>Click on your username/pic to go back to your home page</li>
</ul>
schacon
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-01-31T10:44:27-08:00
Feature Requests - version 2
Thu Jan 31 10:44:27 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I'm putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I'm sure they have to add them.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects</p>
<h3>User Aliases</h3>
<p>I have a couple of email addresses that I use or have used in the past - it would be cool to be able to list them so that any commit with any of those addresses would be associated with my single user</p>
<h3>Little Things</h3>
<ul>
<li>Click on your username/pic to go back to your home page</li>
</ul>
schacon
tag:github.com,2008:Guide/7
2008-01-31T10:41:38-08:00
2008-01-31T10:41:38-08:00
Feature Requests - version 1
Thu Jan 31 10:41:38 -0800 2008
<p>I think we can all agree that the GitHub masters rock. However, there might be a few things that could make the site even more logically awesome. I'm putting up this page just to let the community suggest features so the GitHubbers can ponder if they would like to spend what little free time I'm sure they have to add them.</p>
<h3>Cloning Stats</h3>
<p>It would be pretty cool to see how many people are cloning our projects</p>
<h3>Little Things</h3>
<ul>
<li>Click on your username/pic to go back to your home page</li>
</ul>
schacon