If anyone from Github reads this, a) this looks great, b) add project templates please, so we don't have to recreate the same columns every time. Thanks. <3
You might be able to do this using the new graphql api :)
Announcing new tools, forums, and features
41–50 of 282 posts
Re: Announcing new tools, forums, and features
#42I sent this to support, but the "Files changed" tab in Pull Requests now has an announcement "We've made some change to reviewing code" The "Learn more" button on that banner is a broken link… (It's a good thing this HN post later directed me to the blog post, as now I've learned from that.)
Sorry about that! Is the link working now?
Re: Announcing new tools, forums, and features
#43This 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.
At Waffle.io, we're all about making project management better for engineers. We believe it's awesome that GitHub is investing in this too, and we'll continue to make GitHub delicious :). More here: http://blog.waffle.io/say-hello-to-wafflebot/
Re: Announcing new tools, forums, and features
#44Some 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…
This has been why we don't use github's issues, wikis, and why we won't use their projects. For example if the overall product has a web site repo, server repo, iOS repo and an Android repo then they need to be used as a coherent whole. An issue might be reported against iOS but the cause is in the server, so the ticket would need to be moved. Rinse and repeat for all the other interactions of piece, and that collaborators often don't know (and shouldn't need to) precisely what issues, wikis etc correspond to which repo.
The now defunct Google Code had a very good solution for this. You could create additional "sub" repositories alongside the "main" one. Github already does that for the wiki, but doesn't generalise it to allowing additional ones. I'm somewhat convinced this is because github has the whole "charge by the repository" model, which is at odds for being useful for projects that require multiple git level repos.
Re: Announcing new tools, forums, and features
#45This 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…
It looks like enforcing 2fa in an org (finally!) means anyone who doesn't have 2fa will be booted out (included whoever may be paying for it at the time) with an email explaining why. I'm afraid to tick the box because of this. :o/
Contact everyone, tell them they have a week, then tick the box. If they didn't do it within the week it's either not important to them or they'll add it right quick after you tick the box.
Re: Announcing new tools, forums, and features
#46Was really hoping "forums" would mean users could add dedicated discussion boards to repositories.
Re: Announcing new tools, forums, and features
#47Batched 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…
You can block merges until there's an "approved" code review in the Protected Branches setting. I don't think it has anything like "everyone who reviewed must approve" though.
Re: Announcing new tools, forums, and features
#48Earlier quoted context omitted.
Can we get this updated to this? defunkt didn't post this blog post before TechCrunch talked about it. I'd much rather had linked to it.
OK, we've updated the link from https://techcrunch.com/2016/09/14/github-gets-built-in-proje... .
Thank you! I haven't said it lately, but the team behind this community is great. Quickly becoming my favorite forum.
Re: Announcing new tools, forums, and features
#49Earlier quoted context omitted.
It looks like enforcing 2fa in an org (finally!) means anyone who doesn't have 2fa will be booted out (included whoever may be paying for it at the time) with an email explaining why. I'm afraid to tick the box because of this. :o/
Contact everyone, tell them they have a week, then tick the box. If they didn't do it within the week it's either not important to them or they'll add it right quick after you tick the box.
We have some "shared" users for things like bots, etc.. wonder how to deal with that since we don't want to enable MFA for them. Otherwise I'd be all over this..
Re: Announcing new tools, forums, and features
#50I predict, one day github will host a school.