4 ms·
Would be good to have some options to expose private activity for aggregation then also another option to expose the repo name you are committing to.
by robryan 14y ago
Would be good to have some options to expose private activity for aggregation then also another option to expose the repo name you are committing to.
- jacques_chester 14y agoMaybe. I imagine they'll progressively roll this sort of stuff out, but why hold up the overall feature for the subset like me?
- icey 14y agoFor whatever it's worth, I'm in this subset with you. I use github for all my work now, but > 98% of what I do is in private repos.
- TeMPOraL 14y agoMaybe because it could draw unwanted attention of the presses - you want bloggers to write about awesome new feature, not about the potential implications of a hidden switch and what would happen if it's default state was different. It's easier to roll out such changes after people are already accustomed with the general idea.
- xbryanx 14y agoHeck no. Private is private. I don't want to have to manage another setting.
- TeMPOraL 14y agoAnother setting is not a problem, as long as they give it sane default value.
- bri3d 14y agoSounds dangerous - I don't think my employer would be okay with me exposing how frequently I contribute to our repositories, not due to any crazy paranoia but simply because they haven't thought about the potential outcomes or abuses yet. To add this feature, GitHub would probably additionally have to add the ability to disable it on an organizational basis, and and that point a simple-sounding feature is transformed to a pointy-haired-boss "organizational matrix" level of potentially conflicting settings.
- robryan 14y agoTrue, I guess I am thinking more from a personal interest perspective, like you would glance down a rescue time breakdown, rather than a telling the world. So one possibility would be to have your personal profile view show both.
- chimeracoder 14y ago> Sounds dangerous - I don't think my employer would be okay with me exposing how frequently I contribute to our repositories, Easy fix: the owner of the repository (ie, the organization) can {en,dis}able the feature per-repo.