5 ms·
Yes it is fairly bizarre that Github don't dogfood the issues function. I'm sure they have an internal system that they prefer, but even that internal system co
by jessaustin 11y ago
Yes it is fairly bizarre that Github don't dogfood the issues function. I'm sure they have an internal system that they prefer, but even that internal system could have a public interface. Also, if the internal system is superior then its superior features could be added to the public system so that we could all benefit.
- scrollaway 11y agoWhere are you getting that they don't dogfood the issue tracker? It's a private tracker (private repository) but from what I've seen in the Github blog, they do... it wouldn't make much sense if they didn't.
- jessaustin 11y agoIf they're using it, they're doing so in completely different fashion than everyone else. That is, it's not public for viewing, submitting, commenting, etc. Indeed TFA indicates exactly the sorts of pain points that would be missed by those using the tool in such a radically different way than everyone else. If someone at GH had to wade through all the damn +1's then something would have been done about them years ago.
- joelhooks 11y ago95% of all my github activity is in private repositories.
- Splendor 11y agoDo you feel like your usage is typical?
- jeddawson 11y agoDitto. Maybe 98%. I think that's a big part of the disconnect I'm seeing here in the comments. Those of us that live in private repos are likely pretty happy with how things currently work especially since we're the ones paying to use the service. If it wasn't working well for our teams, we'd find somewhere else to spend our money. That being said, we're certainly the minority when it comes to users on the platform.
- cookiecaper 11y ago>That being said, we're certainly the minority when it comes to users on the platform. But you're the huge majority of people who give GitHub money. It makes sense not to prioritize the pain points of open-source projects when you lose money by hosting them.
- Kudos 11y agoI only pay Github money to host my private repos because their platform also hosts most of the open source projects I use. If enough of those projects leave for a service that does open source better, I'll be happy to follow them. Otherwise I may as well be using Bitbucket or Gitlab.
- fweespeech 11y agoWe don't pay GitHub precisely because they lack features we can implement in GitLab. Much of that is due to the OP's requested features that are currently missing. But tbh, it is too late to get us to switch. > Issues are often filed missing crucial information like reproduction steps or version tested. We’d like issues to gain custom fields, along with a mechanism (such as a mandatory issue template, perhaps powered by a newissue.md in root as a likely-simple solution) for ensuring they are filled out in every issue. For instance, is something we basically implemented in our local version of GitLab but aren't sharing because our implementation pulls this from internal docs other people can't use. Our CSRs put issues into GitLab but they tend to forget steps while on the phone with a user. We wouldn't have bothered if we had something like this when I was evaluating GitLab vs. GitHub.
- krschultz 11y agoWe have the diamond level plan from GitHub and have >260 private repos at my company. We only chose GitHub because we wanted to host our open source repos there. If they don't prioritize the open-source projects then we have no reason to pick them over BitBucket or something else like that.
- kelseydh 11y agoThat's not how it works. Happy consumers leads to happy enterprise users. They are one and the same.
- gabriele 11y agoGitHub pretty please, give us an option to hide our profile from search engines just like Facebook do.
- hk__2 11y agoWhat is the use-case of this?
- gabriele 11y agoI have an account that is only for private repos and I don't want that account to appear on search engines for my real name. I also have a public account that I use for contributing to public projects so it could also help to avoid duplicate accounts in search results. All accounts should be searchable for username/real name with GitHub's search anyway.
- Alupis 11y agoJust curious, why not have just a single account? Your private repo's and contributions are not made public, so there's no "risk" involved.
- shampine 11y agoI think a lot of companies forced this because for a while the api permissions weren't granular enough when dealing with private repos on organizations. They added the "Third-party application access policy" sometime in the last year or two. I might be wrong though.
- BinaryIdiot 11y ago> If they're using it, they're doing so in completely different fashion than everyone else. That is, it's not public for viewing, submitting, commenting, etc Huh? Github isn't opened sourced so how is a different fashion from anyone else using private repos?
- donarb 11y agoI would guess that private repos have a much smaller user base, in that that they work for companies where they are trained in specific policies to submit issues and work with the repos. With public repos you're at the mercy of widely differing levels of user experience.
- Kiro 11y agoI think you should chill down with all the speculations. I only use it for private repos.
- kelseydh 11y agoGo look at a project like Rails where you can tell they need it.
- johnmaguire2013 11y agoPlenty of private projects use a separate, public Github repository for community reporting of issues, and public tracking of those issues.