Better integration and monetization of Github Apps (formerly Integrations)?
GitHub announcements: Marketplace, Apps and GraphQL API
51–60 of 166 posts
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#52I guess that the main benefit of GitHub Marketplace would be the full-scale integration with GitHub Issue and Project board, launched last year. Consider a common situation: when CI fails, people need to reopen an issue manually, getting an error report via email. People who are in charge of project management may be seeking a better way to streamline the manual task, which probably increased since the introduction of Project board.
To be clear, I’ve been away from software development over the years, so I’m curious about the impact of Project board. Does it useful in the first place? Did it require manual tasks between other services such as CI? Do you, who is in charge of issue or board assignment, feel frustration using it?
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#53How about communities, forums, boards? When I see an interesting project I'd like to talk to the developer without cluttering the Issues section. It could be the entry point of every repo, moderated by the owner of course (something like php docs where people can post interesting stuff related to the page at the end). And it would make Github more social.
I think a dev-social site like that should be separate to GitHub and just use their API to pull in repo data.
Someone should probably give a go at making a site like that. Making it easier for project owners to find contributors and for potential contributors to find projects. Facilitating discussions beyond in issues, etc.
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#54I expected GitHub to attempt further monetizing but perhaps not something as cheesy as an "app store".
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#55Earlier quoted context omitted.
I have, a lot, and when I could only GET kinds of hierarchical data instead of lumping nested queries, I turned to graphQL (or a, er, homegrown subset of it - it had just been announced) to fill in the gaps. It turns out that most software doesn't, really, care about asking for or updating 'state' per se , and the amount of awkward munging you have to do interpret every kind of query as 'asking about state' is, in my…
Again, the problems you describe with REST are a limitation of your implementation, not of REST itself. GraphQL itself is built on top of REST via a single GET/POST query endpoint. The difference between it and typical REST implementations is that the resource identifier and fields to return have been moved into a novel query syntax. However, the same result can be achieved with a typical REST endpoint combined with…
GraphQL uses a single endpoint for the entire API. It would be a POST to /graphql, there would be no /users/123 resource.
GraphQL is a form of RPC, it's not REST.
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#56How about communities, forums, boards? When I see an interesting project I'd like to talk to the developer without cluttering the Issues section. It could be the entry point of every repo, moderated by the owner of course (something like php docs where people can post interesting stuff related to the page at the end). And it would make Github more social.
I think a dev-social site like that should be separate to GitHub and just use their API to pull in repo data. Someone should probably give a go at making a site like that. Making it easier for project owners to find contributors and for potential contributors to find projects. Facilitating discussions beyond in issues, etc.
Like gitter ? But more similar to Discourse.
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#57Earlier quoted context omitted.
REST and GraphQL are two completely different things, and one is not a replacement for the other. REST is an architectural concept, whereas GraphQL is a query language spec. https://philsturgeon.uk/api/2017/01/24/graphql-vs-rest-overv...
That's true in theory, but in practice REST is a (limiting) spec for the kinds of verbs you're allowed to use between systems, and graphQL is a significant and much needed expansion of that.
GraphQL is limiting as well, just in a different way. GraphQL uses POST by default, which means you don't get browser caching.
It's a tradeoff that makes sense for Facebook. It allows them to make changes to their API without needing to version it. And they can take the hit of more requests hitting their server. For most apps though, I think the tradeoff is probably not a great one to choose.
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#58Congratulations to the GitHub team for a great release here on the new Marketplace. I'm Matt - CEO at ZenHub [1], one of the launch partners for the Marketplace. We've been building apps on top of the GitHub platform for 3 years now and watching the evolution has been amazing. The three releases here have really helped with our biggest integrator pain points: GraphQL - better and faster access to data without hitting…
Zenhub is great Matt, good to hear it's beneficial to you :) I'm going to recommend it to others here, with a caveat: I really wish it would not be so aggressively hijacking the Github UI. Tabs and side panels move around because the JS on the page finishes executing, making the Github UI feel super sluggish. We also have a lot of projects which end up with the settings tab in a "More" dropdown, despite Boards and Re…
Thank you for the kind words - and the honest feedback! This are similar to thoughts we have heard for other users and we are working on better ways to give you more control over the UI in the near future
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#59Hm, I like Github but I don't like this. This is a great move, but we already have a code hosting monoculture, and this subtly piggy-backs on it towards lock-in for tooling. Github knows orgs have inertia. Sorry for the slippery slopeism. I'm just imagining a future where shipping an app without a middleman moves to inconvenient, then annoying, then difficult, then impossible. Because this is exactly how we lost the…
Bitbucket has more traction than you think. Especially in megacorps who use JIRA. As long as the services have a docker container you can run locally I see no lock-in.
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#60I'm Tomek, CEO at codebeat [1] - automated code review for the web & mobile and one of the launch partners for the GitHub Marketplace. For us and probably for many tools that integrate with Github, an announcement about Github Apps is great news because we won't need to ask users for so many permissions.
GraphQL also seems to be an interesting way to combine more data available on Github with results of our code analysis.
I think Github Marketplace is a right fit for Github and community because it lowers the barrier to use third-party tools. Github puts them in one place, and it is super easy to add or remove each of them.