That helps with the code hosting, but what about a wiki? Bug Tracker? Communicating with other devs? A bitbucket or github repo helps with all of these things too.

Absolutely. But for most casual projects, YAGNI.

You'd have to be pretty casual not to want a bug tracker - even for completely internal, non-public facing, one dev projects they're invaluable for keeping things straight, tracking todos, etc.

That said, I think there's definitely a use case for some sort of bug tracker/wiki which can be embedded in a repository, a'la Fossil. Perhaps flat files rather than SQLite though, so you can track changes in your repository. Not sure how you'd get changes in though, other than via a pull request.

    # TODO
    * add foobar support
    * remove baz
    * refactor quux to be more QUUUX-compliant

Why use a web interface for what a text file does fine? You aren't sharing with anyone, so you don't need collaboration capabilities.

Depends on your project, but you might want at least some level of visibility. If not now, then at some point in the future. Plus, the issue tracker and wiki are currently not versioned or linked to your code, so there's the possibility of them going out of sync.

Many years ago, I wrote a web application that provided this file via a FUSE interface and an online interface you could share with your friends.

Nobody was interested. All the good programmers I know have a simple text file or a mental TODO list. This added too much complexity. On the other hand, all the managers I know want checkboxes and reports and auditing and ..., which made this too simple.

So just use a text file.

Obviously you don't know me, but the implication that I'm not a "good" programmer because I like some of the features that an issue/task tracker provides over a text file is silly. Jira + Mylyn + Eclipse makes identifying which commits were related to what task just a few clicks away. Likewise I can open a ticket and Eclipse automatically opens all the files I was working with last time I worked on that ticket. If one of my friends wants to help out, I can just assign him a few tickets, and he gets the same benefits, plus I can know what he's working on ATM and what's been completed. Handling customer/client issues in a trackable public way is great, and easy release notes with links to the tickets are way better than cutting/pasting some text todo list.

Pit is a command-line project manager that integrates with Git http://github.com/michaeldv/pit

Cool project. That's pretty much what I had in mind, except maybe some sort of lightweight wiki, too.