GitHub announcements: Marketplace, Apps and GraphQL API
41–50 of 166 posts
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#42Re: GitHub announcements: Marketplace, Apps and GraphQL API
#43No CI? Gitlab and Bitbucket have built-in pipelines.
https://github.com/marketplace/category/continuous-integrati...
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#44Earlier quoted context omitted.
You should read about REST then :)
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…
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 a sparse fieldset query parameter [1]:
/users/123?fields=name,email,work.name,work.address
where "work" is a sub-resource in the same vein as GraphQL. The difference between this and GraphQL is purely syntactic: user({ "id": 123 }) {
name,
email,
work {
name,
address
}
}
[1] http://jsonapi.org/format/#fetching-sparse-fieldsetsRe: GitHub announcements: Marketplace, Apps and GraphQL API
#45Hm, 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…
FTA: "More than a dozen integrators have apps in GitHub Marketplace today, including Travis CI, Appveyor, Waffle, ZenHub, Sentry, and Codacy"
Travis CI and many others were widespread prior to this marketplace. Seems to me that creating a marketplace is a logical way to collect these third-party services in one place.
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#46If I install a free version and hit the limit does it auto upgrade me and charge me or am I just cut off from the service and told I should upgrade to keep using it?
What happens today is the limits are enforced on the app side, not he GitHub side.
So for example our free plan is two users. If you wanted to add a third you'd need to go GH Marketplace and upgrade to the eg 10 user plan. That would trigger an upgrade in Codetree and your plan there would enable you to add up to ten users.
In short: you trigger upgrades and downgrades, not the tool vendor you're using or GH, and thresholds are stored in the tool vendors database so they're the ones who decide how to tell you that you need to upgrade.
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#47If I install a free version and hit the limit does it auto upgrade me and charge me or am I just cut off from the service and told I should upgrade to keep using it?
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#48The Github team was great and tireless during this launch, congrats to Github and all the partners.
I'm Jaime, CEO of Codacy[1] and one of the three chosen Code Quality partners for this launch. We specially love the Github Apps, since we heard for a long time the feedback of asking too many permissions. This has been a bit of a pain point. With Github Apps, it will be easier to cherry pick permissions. This is not yet running in Codacy but it will soon.
One of the reasons why we're excited and decided to take part is the really qualified audience. Everyone just really gets what we do (automated code review) when they are already familiar with Github.
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#49Earlier quoted context omitted.
> You can only stage all changes in a file If I'm understanding you correctly, this is wrong. You can add individual lines in a file to your commit. That's one of the main uses I have for the app: it's easier to split up file changes between commits than on the command line. See this screenshot: http://imgur.com/a/4CQG7 You have to click on the line numbers to add/remove individual lines.
Not a very obvious UI!
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#50Earlier quoted context omitted.
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.