6 ms·
GitHub releases integrated issue tracking
- defunkt 18y agoIt's not git-backed (yet), but if you're interested in something like that check out Ditz (which you can use with GitHub's Pages feature): http://en.deadbeaf.org/2009/04/17/ditz-on-github-page/ http://en.deadbeaf.org/2009/04/17/ditz-on-github-page/
- lux 18y agoAwesome! I was hoping for this for some time. Lighthouse user right now, but putting the two together just makes sense. I setup a new repository last night and saw an option for "issues" in the settings, so I'm not so surprised but definitely happy :)
- old-gregg 18y agoI like GitHub a lot and have been waiting forever to open an account there. As soon as they get their act together and make every page load in milliseconds as opposed to seconds, we're dumping our own git server.
- defunkt 18y agoWhere are you located? Most git pages (e.g. http://github.com/rails/rails/tree/master http://github.com/rails/rails/tree/master or http://github.com/rails/rails/commits/master http://github.com/rails/rails/commits/master) should load fast. That said, we're still working hard to optimize and speed-up every aspect of the site. The dashboard in particular should get a massive speedup soon.
- WALoeIII 18y agoThis solves 80% of Open Source project needs. More robust ticketing ala Lighthouse will still have a place for bigger projects. Good work Logical Awesome.
- capablanca 18y agoSucks for the GitBug guy that launched just a few days ago
- icefox 18y ago"Gitbug is an in-repo bug tracker for Git repositories." So that still makes it a very interesting project. GitHub's issue tracking is not bt integrated into the repositories from what I can tell. link: http://github.com/kig/gitbug/tree/master http://github.com/kig/gitbug/tree/master
- capablanca 18y agohttp://gitbug.appspot.com/ http://gitbug.appspot.com/ (Not that he lost money)
- hboon 18y agoTime almost always costs more than hosting.
- icey 18y agoSomewhat unrelated, but are there any good graphical Git clients for OS X?
- mojombo 18y agoTry GitX: http://gitx.frim.nl/ http://gitx.frim.nl/
- davidmathers 18y agoAnd/Or gitnub: http://wiki.github.com/Caged/gitnub http://wiki.github.com/Caged/gitnub GitX is more useful, but I prefer the IA of gitnub for history browsing.
- tortilla 18y agoI like Gitx better, but check out gitnub
- tlrobinson 18y agoExcellent! This is great for small to medium sized projects. I see very little reason to use anything other than GitHub for new open source projects. Here's an easy improvement: how about integrating a CLA submission form, so contributors can easily e-sign a project's CLA, and project managers can easily see who has signed the CLA.
- boucher 18y agoSeconded. This is a pain to deal with, and integrating it with Github would be oh so nice.
- icefox 18y agoWhat is CLA?
- tlrobinson 18y agocontributor license agreement, to assign or license IP to the project you're contributing to: http://en.wikipedia.org/wiki/Contributor_License_Agreement http://en.wikipedia.org/wiki/Contributor_License_Agreement
- davidw 18y agoTo add a bit more, these are required by some projects/groups, such as the Apache Software Foundation, for legal ass-covering purposes.
- uggedal 18y agohttp://bitbucket.org http://bitbucket.org has had issue tracking for ages.
- technoweenie 18y agoSo has sourceforge.
- zacharypinter 18y agoAny idea how this will work with forks and branches? Right now it looks like it's a separate set of issues for each user/project combo. How will that work when u merge somebody else's commit that says "close #1"?
- defunkt 18y agoOnly collaborators can close tickets, so if you merge in commits from someone without permissions the 'close #1' will have no effect.
- arohner 18y agoIs there a page that documents how merge tracking on bugs works right now, and what's on the roadmap? Good merge tracking could push me over the edge for signing up for a paid account.
- r11t 18y agoThe issue "voting" feature seems to have been inspired by HN!
- grandalf 18y agothis is awesome... now to figure out how to upload our retrospectiva issues list into it :)
- donw 18y agoIs there an API for the issue tracker? I could think of a use for this right off the bat...
- tvon 18y agoThey're certainly are this generations Sourceforge. I couldn't care less about git[1], honestly, but github is extremely nice. [1] Obviously some things would be more difficult with say, svn, but my point is, I use git to use github. (edit, missing word, edit2, stupid asterisk formatting)
- jonursenbach 18y agoYeah I have some problems handling git as I'm used to svn. It'd be nice if they expanded to the other version control systems that are out there. Wasn't there a rumor not long ago that they had registered svnhub.com or mercurialhub.com? My memory escapes me.
- jpcx01 18y agoI think they'd benefit much more if they used their position as the killer git app in order to help git go mainstream. Having git be universal in the Ruby/Rails world has been a huge accellerator for maintaing open source projects. No longer are we subject to core teams losing interest, anyone can fork and become the new core team.
- davidw 18y agoAnyone at all can and does fork, which, yeah, is great and all, but until they fiddle some more with the UI or something, makes it really difficult for other people to figure out who the heck the core team is. It's not like it wasn't possible to fork stuff in the past, it just required a little bit more effort... enough so that you didn't just get random copies of stuff all over the place. I wonder if you get a projects bugs if you fork it?
- tvon 18y agoIt's kind of the nature of the beast. If you make forking and merging simple, people will do it on a whim. An indicator for the original code would maybe be useful, but it would lead to confusion when, for example, the original maintainers fade away and another repo becomes the pseudo-canonical tree.
- benhoyt 18y agoGitHub does look cool. However, I'm wondering what advantages Git will give me over Subversion for small and medium-sized projects? I guess I'm really asking what's the advantage of distributed version control over centralized for Joe Coder. Distributed VC seems quite different, and I'm wondering whether it's worth the time to learn. Or should I just get on with writing code using the VCS I'm used to?
- cbryan 18y agoBranching! The way that git deals with branching is great. I'm a real fan of the way that it lets me context switch. This feature isn't a result of git's distributed nature, but I think it's worth switching VCS's for. One of the advantages it certainly gave me is that there isn't any difference between the local and remote repositories. There aren't any daemons to start and no infrastructure to keep up; just initialize your repo and go!
- adbachman 18y agoExtremely lightweight repository creation is my reason. `git init` and you've got a local repo. One .git folder in your root directory and that's it. Blow away the one folder and you're back to where you started. None of the .svn folder spam you get with subversion. There are a few differences in commands and concepts, but you can keep it simple and the experience is about the same for small to medium independent projects.
- jpcx01 18y agoWow, this is incredible. I really like the voting & fast access keyboard shortcuts. Alright github, I forgive you for all the downtime!
- oomkiller 18y agoThis is pretty cool, it would be nice if they had an api so we could sync with Lighthouse etc.
- icefox 18y agoAfter a few minutes of playing around: * There does not seem to be any documentation * What are keywords to close a task in a commit. Does it have to be in English? Can the words be customized? * Can I import from external projects (i.e. Everyone on github uses something else today and needs to migrate) * Where are issues stored? Are they stored in a git repo? * Can I export? * When you make a label shouldn't it pick a color automatically? * What about when I merge issues from forked projects, when they Close task #12 is that their #12 or my #12? * If I rebase and remove a commit that fixed #12 will the issue be updated? * If you fork someones repo do you get the issues? What about when you pull and rebase? How are they merged? * Can I see if any of my forks have fixed issues? * What branch does the issue tracker look in to see if an issue has been fixed? master? Is it customizable? It looks nice, but after poking at it for a minute I am a bit underwhelmed. It is a nice basic and traditional issue tracker, but at least what is exposed is no where near any of the interesting issue trackers built on top of git that people have been playing around with the past year. Maybe it is all built on git and that will be revealed as time goes on, but not sure. Hopefully it wont stop some of the people who have been playing around with issue trackers built on top of git. Part of the joy of Git is that I am not tied to GitHub. Yes I host my projects there, but when it goes down it doesn't matter because I can still keep working. I was really looking forward to a issue tracker that is built on git that I can store in my project tied into GitHub. But this is till very cool and a good step in the right direction.
- vamsee 18y agoAbout time. Never really liked Lighthouse.