Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Announcing new tools, forums, and features

github.com

Post reply on HN
Print view View original

21–30 of 282 posts

Re: Announcing new tools, forums, and features

#21

Post by bhuga »

bsimpson wrote: post #9

I'll be curious to see if they've made API granularity more sane. We haven't been able to use any third party tools because our security people don't feel great about giving third parties write access to everything (including our source) for tools that don't need it. In the past, GitHub hasn't differentiated write access to issues (which many tools need) and write access to the source itself (which basically nothing…

This is an important part of the new integrations early access program: https://developer.github.com/changes/2016-09-14-Integrations...

Re: Announcing new tools, forums, and features

#22

Post by [deleted] »

bsimpson wrote: post #9

I'll be curious to see if they've made API granularity more sane. We haven't been able to use any third party tools because our security people don't feel great about giving third parties write access to everything (including our source) for tools that don't need it. In the past, GitHub hasn't differentiated write access to issues (which many tools need) and write access to the source itself (which basically nothing…

[deleted]

Re: Announcing new tools, forums, and features

#23

Post by avitzurel »

Batched review and pending state have both been a long time coming.

Most of the times when I do a review it's not a single comment and right now the workflow is to let the team know on Slack that I am reviewing this.

From the Gif it's not 100% clear what the pending state does but I would want something like blocking the PR until every team member that started reviewing will "release" the PR. I also see the negative side of this of course but I think the positive outweighs the negatives.

Re: Announcing new tools, forums, and features

#24

Post by thegarside »

captn3m0 wrote: post #17

This is a rough summary of what all I read in the blog post: 1. projects. replaces trello, waffle.io, zenhub and many other similar services. 2. code reviews allow approval/request changes as sunny's screenshot shows 3. reviews can be made mandatory. 4. github platform integrations is getting a roadmap 5. a graphql api to query their database 6. enforce 2fa in organizations (much love for this one) 7. summarized time…

Doesn't look like Projects comes close to replacing ZenHub / Waffle.. Not for proper teams anyway – real project management needs to be much more robust so I'm keeping ZenHub for now.

Re: Announcing new tools, forums, and features

#25

Post by moby »

BinaryIdiot wrote: post #13

The review stuff is semi similar to what I requested GitLab do and I'm surprised it's taken so long for anyone to really do it. It's a great workflow. I'm still not convinced about keeping all of your project's management in the version control system (I mean I prefer issues in there but the rest seems...wrong to me for whatever biased reason I have). Overall looks good! When does Enterprise get these features? :)

We're glad you like it! This is the first of many Code Review enhancements we'll be providing, so stay tuned.

These features will be coming to GitHub Enterprise soon - we always aim to get new features onto the Enterprise platform on the next major release (which occurs every 3 months on average).

Re: Announcing new tools, forums, and features

#26

Post by jglovier »

captn3m0 wrote: post #17

This is a rough summary of what all I read in the blog post: 1. projects. replaces trello, waffle.io, zenhub and many other similar services. 2. code reviews allow approval/request changes as sunny's screenshot shows 3. reviews can be made mandatory. 4. github platform integrations is getting a roadmap 5. a graphql api to query their database 6. enforce 2fa in organizations (much love for this one) 7. summarized time…

>projects. replaces trello, waffle.io, zenhub and many other similar services.

This is really not about replacing those services, it's more about building a better foundation for integrators like Waffle and ZenHub to build on.

Re: Announcing new tools, forums, and features

#28

Post by rohamg »

sgarrity wrote: post #16

Some nice improvements here. It appears, though, that Projects suffer from the same problem we've had with Issues: they are limited to one repo. I know there are some tools to manage Issues across repos, but for the most part, the tools seem to assume you work on only one repo, or that milestones only affect a single repo. I would love to see projects/milestones become more capable when dealing with cross-repo issues…

Take a look at ZenHub [1] - it lets you stay inside GitHub, but adds much more full-featured project management capabilities including multi-repo boards and advanced reporting features like estimates, issue hierarchy (epics), personal to-dos, burndown and velocity charts, etc.

[1] https://www.zenhub.com

Re: Announcing new tools, forums, and features

#29

Post by web007 »

bsimpson wrote: post #9

I'll be curious to see if they've made API granularity more sane. We haven't been able to use any third party tools because our security people don't feel great about giving third parties write access to everything (including our source) for tools that don't need it. In the past, GitHub hasn't differentiated write access to issues (which many tools need) and write access to the source itself (which basically nothing…

Plus a million - I'm not sure how this still isn't a feature.

Considering all of the PCI-DSS / HIPAA / SOX / etc. audit points around change control (even ignoring corporate versions of the same) it's practically impossible to add external services to GH and have them be useful while still meeting compliance. Change control is required, but that also implies control of change control. As-is any service could delete all of your content, whether intentionally or inadvertently, or even worse could corrupt or otherwise alter your history.

It may be detectable and recoverable because git, but it would be infinitely easier to have code and PR be r--rw-.

EDIT: This is now a thing, according to @bhuga below. Also, GH is now publishing a roadmap for what's coming down the pipe, so we're not in the dark as to when these critically-important-why-isnt-it-out-yet features are being worked on. https://developer.github.com/early-access/platform-roadmap/

Post reply on HN