Give us only what we need!

Hey, guys! The past week’s been all about fixing things.

I had to fix my broken laptop, broken coala plugin, etc. Of course, everything has a silver lining. It’s my first week into the official Coding Period of ☀️ Google Summer of Code 2017. I’ve been working on implementing a few interfaces for GitLab on IGitt. It’s all about reading API documents, testing and following the implementation based on GitHub.

However, there’s a keen difference in how they handle issues and pull requests. GitHub unifies them into something called **/pulls** which therein handles the API for both of them. On the other hand, GitLab has a unique internal identifier for each of them separately to handle requests. And there was already Maxmillan Scholz who already wrote some of the interfaces for GitLab in IGitt, however GitLab migrated their API to v4. So, we gotta rewrite them again. It’s been quite fun working with the APIs, a few bug fixes here and there. I’ve been rewriting the interfaces for **MergeRequest**, **Commit**, **Issue**, **Comment**, **Repository**, **Hoster**, etc. on IGitt for GitLab. I’m so lost into GSoC. 😏

Now off to the original blog title. It speaks for itself, GitHub has terrible permission schema for OAuth applications. They don’t provide read only access to repositories, which is all what we require to clone it and read it’s labels, etc. They have a scope, **repo** which grants read and write access to both private and public repositories of the user. Thus scaring him away about potential loss of data. GitLab takes this to the next level 😤 by giving just two scopes, **user** and **api** , the latter gives access to almost everything even deleting repos, ‘cuz, why not? 😠

Oh, I almost forgot! I got my first Mac now. 😎 The 2016 13" Retina Macbook Pro with TouchBar. Back to macOS again. This time with Mac prowess.

Signing off, Naveen Kumar Sangi.