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

GitHub announcements: Marketplace, Apps and GraphQL API

github.com

Post reply on HN
Print view View original

11–20 of 166 posts

Re: GitHub announcements: Marketplace, Apps and GraphQL API

#11

Post by kareemm »

venning wrote: post #9
kareemm wrote: post #6

I'm a partner at Codetree[1], one of the four launch partners in the project management category of GitHub Marketplace[2]. Happy to answer questions about our experiences working with the GH team to integrate, why we decided to list in Marketplace, etc. [1] - http://blog.codetree.com/articles/project-management-launch-... [2] - https://github.com/marketplace/codetree

You might be the wrong person to ask, but I can't really find anything about this elsewhere: As an App/Integration, is your interaction with the GitHub interface itself limited to only those things that you can do via API calls, such as creating new issues? Or do you have some capacity to modify or add on to the existing interface?

As far as I know there's no capacity to add onto the existing GH interface - all interaction is via APIs and webhooks.

Re: GitHub announcements: Marketplace, Apps and GraphQL API

#13

Post by bkeepers »

davidjgraph wrote: post #2

"...fine-grained repository permissions with GitHub Apps...", excellent, this caused us more problems integrating than anything else. Especially for an organization, anything beyond 15-20 repos and they just couldn't give permission. Edit: It only applies to Github Apps, we have an OAuth App. shame.

GitHub Apps also support authenticating users with OAuth, so you might want to check out if it makes sense to migrate.

https://developer.github.com/apps/building-integrations/sett... https://developer.github.com/apps/building-integrations/sett...

Re: GitHub announcements: Marketplace, Apps and GraphQL API

#14

Post by nailer »

After trying new GitHub Desktop Beta mentioned in the article a week ago: it's still nowhere near compete enough to work:

- You can only stage all changes in a file - so you can't discard 'console.log('Wooo'); debugger;' when committing, you have to remove those in your editor first, then commit.

- you can't reverse commits. Need to roll HEAD back to a previous commit, push those fixes, then resume what you were working on? You can't do it.

- still no graphical interactive rebase to merge and squash and reorder commits (the main reason people put up with sourcetree).

It feel fast and responsive though.

Edit: downvotes seem odd. If you think this is offtopic, the GitHub Desktop Beta is announced in the article.

Re: GitHub announcements: Marketplace, Apps and GraphQL API

#15

Post by LeanderK »

23david wrote: post #8

"Once your revenue reaches a minimum of $500 USD for the month, you'll receive an electronic payment from GitHub for 75% of the sales price." So it looks like Github takes a 25% fee. I thought maybe they would do something more innovative regarding the fee structure, or maybe have a lower intro fee like 15%. But here is seems pretty much on par with the 30% of the Heroku marketplace.

Wow, i think 25% is more than enough, they don't have costs that justify 25%. It's just their monopoly that allows them to charge that much.

Re: GitHub announcements: Marketplace, Apps and GraphQL API

#16

Post by nailer »

m12k wrote: post #7
therealmarv wrote: post #3

I did not followed recent GitHub news closely. Is GraphQL a new thing at GitHub? And do you think GitHub integration benefits from this?

GraphQL is a method of creating APIs for consumption by e.g. JavaScript apps or mobile apps that is gaining popularity at the moment. So it can be seen as a successor to REST. It gives you a pretty easy query language to specify which data on which objects you are interested in and that data is then fetched for you. An example could be a React app where each component specifies which data it needs to work on, and the…

The main thing vs REST is that it fixes the 'overlapping data in resources' issue. Want a timeline of tweets? Well you'll also want avatars to display, and you probably don't want that in a separate resource (because of multiple requests), so both /tweets and /users/userid will give you avatar details. It's a bit messy.

In graphQL there's one resource and you query it to tell you what you want.

Re: GitHub announcements: Marketplace, Apps and GraphQL API

#17

Post by bradleyankrom »

LeanderK wrote: post #15
23david wrote: post #8

"Once your revenue reaches a minimum of $500 USD for the month, you'll receive an electronic payment from GitHub for 75% of the sales price." So it looks like Github takes a 25% fee. I thought maybe they would do something more innovative regarding the fee structure, or maybe have a lower intro fee like 15%. But here is seems pretty much on par with the 30% of the Heroku marketplace.

Wow, i think 25% is more than enough, they don't have costs that justify 25%. It's just their monopoly that allows them to charge that much.

Monopoly in what sense? There is certainly healthy competition in the hosted Git repository space.

Re: GitHub announcements: Marketplace, Apps and GraphQL API

#18

Post by mpetrovich »

m12k wrote: post #7
therealmarv wrote: post #3

I did not followed recent GitHub news closely. Is GraphQL a new thing at GitHub? And do you think GitHub integration benefits from this?

GraphQL is a method of creating APIs for consumption by e.g. JavaScript apps or mobile apps that is gaining popularity at the moment. So it can be seen as a successor to REST. It gives you a pretty easy query language to specify which data on which objects you are interested in and that data is then fetched for you. An example could be a React app where each component specifies which data it needs to work on, and the…

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...

Re: GitHub announcements: Marketplace, Apps and GraphQL API

#19

Post by avaer »

Hm, 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 ability to send email without paying the middleman privacy tax.

Re: GitHub announcements: Marketplace, Apps and GraphQL API

#20

Post by k__ »

avaer wrote: post #19

Hm, 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…

Yes, seems a bit like Bitbucket/Jira stuff, and I don't know many people who liked it.
Post reply on HN