Looking for repository hosting solution with specific requirements
I need a platform that combines Git repository hosting with issue management, similar to what GitHub offers, but with one key difference. I want to keep my source code private while making the issue tracker accessible to the public.
I’ve already tested several options including Gitorious, Unfuddle, and Codebase, but none of them quite fit what I’m looking for. I’m open to paid solutions if they have the right features.
Self-hosting is also an option if there’s existing software that supports this configuration. The important thing is that everything stays within one project rather than splitting it across multiple platforms.
Has anyone found a service or tool that allows this kind of setup? Any recommendations would be helpful.
Azure DevOps handles this really well. You can keep your repo private but make work items (basically their version of issues) public. The permissions are granular enough to let anonymous users view and create work items without seeing any code. I made the switch about two years ago after getting frustrated with other platforms. The interface is weird if you’re used to GitHub, but the access controls are solid. Works great with Microsoft tools, though it’s fine on its own too.
bitbucket has this built-in if u check the permissions settings. you can make the repo private but keep issues public - took me ages to find tho. way easier than dealing with self-hosted solutions.
Been dealing with this exact thing at work lately. Managing separate permissions for repos and issues manually turns into a total nightmare fast.
You need automation to handle private code with public issue tracking. I built a workflow that syncs issue data automatically, manages permissions, and keeps everything centralized without the headache.
Best part? It connects to whatever Git hosting you’re already using and automates the whole process. No more jumping between platforms or wrestling with permission matrices. Set it once, let automation handle everything.
I’ve watched teams burn weeks trying to configure GitLab or Gitea for this. Skip that mess and automate from the start.
For your requirements, GitLab is an excellent option. It allows you to maintain private repositories while making the issue tracking feature accessible to the public. If you’re considering self-hosting, Gitea is also a viable choice, as it supports anonymous access to issues while keeping the source code private. Both platforms should meet your needs effectively.
GitHub actually supports this through organization settings, though it’s not obvious. Set the repo to private, then enable public issue access under repository settings > Features. The tricky part is getting the access levels right - took me several tries when I needed this for an open source project with proprietary dependencies. Their docs suck for this specific case, but once you get it working it’s seamless. Way better than juggling separate platforms or dealing with self-hosted setups.