Bidding farewell to Google Code

Re:Bidding farewell to Google Code by z1mm32m4n on Friday March 13, 2015 @04:01AM (#9196063)

> Github for example only lets you have one source repository per project, and as a result the wikis and issues are useless since they are almost always filed against the wrong sub-project.

You can disable the wiki and issues pages on a repository-by-repository basis. If you're looking to solve the issue of issues being filed in the wrong place, you could try to pick the component that is the most central or most front-facing and only leave that wiki or issue tracker enabled. Then you'd just add a simple note in the README of the other repos about where to go to report issues or read documentation. It's definitely not the same, but it is a somewhat elegant workaround.

[ Parent | on HN ]

Re:Bidding farewell to Google Code by rogerbinns on Friday March 13, 2015 @12:23PM (#9197977)

This doesn't help for the issues. With commit messages you can reference or close tickets (eg "fixes #73"), but that won't be available if committing, unless in the one repo that does have issues enabled.

[ Parent | on HN ]

Re:Bidding farewell to Google Code by abraham on Monday March 16, 2015 @01:37AM (#9210032)

You can reference issues in any repo with "ref username/repo#73"

[ Parent | on HN ]