GSoC coding Phase 1 ends

-

Coding Phase 1

Week 4

Fixes vs Closes:

I started working on adding a new feature in existing pull request(PR) auto review plugin, called "Fixes vs Closes checking". In coala, for every PR we make, we have to mention which issues we are trying solve, in commit message. We should use `Fixes issue_link`, if we are fixing a issue which has a `type/bug` label and use `Closes issue_link` if we are closing a issue which doesn't have a `type/bug` label. So, I have written code to do this automatically by GitMate, if commit message doesn't follow the guideline, then GitMate will remove the PR from review queue by removing `pending review' label, adding `work in progress` label to the PR and configurable comment will be added on the PR explaining what was done wrong. I have also made  IGitt enhancement to know which keywords(Fixes, Closes) referenced which issues. 

PR Rejector:

I mentioned in the previous blog post about having some issues with testing migrations while working with PR rejector plugin, Naveen(my mentor) fixed that error and my PR got merged. One of GitMate users asked for feature disabling PRs with a comment in GitHub. As per the request I worked on adding a regex option for branch names, so that user can give a regex that matches anything and any PR opened will be closed and GitMate will comment on the PR as configured by the user.

Squash:

As I said in the previous, I have written code for GitMate responding to comments requesting for squashing commits in the PRs. In this week, I started writing code for running squash command, in mr-rebaser, which clones repo of user and perform required operations on the repo and push it to the user repo in the name of GitMate-bot. Most of the code was completed, but there were some errors regarding giving commit message via command line and splitting command line arguments as needed.

I worked a lot on adding different plugins this week and faced several errors, making me learn a lot of new things. As always Naveen helped whenever needed throughout the week. I submitted my first evaluation of the mentors and I will be receiving the same from my mentors. With this Google Summer of Code(GSoC) Coding Phase 1 has ended. Let's see if I will pass my first evaluations and continue to phase 2 or not, in my next blog post.

Comments

Post a Comment

Popular posts from this blog

GSoC coding phase 2

-
Image
Coding Phase 2 Phase 1 result GSoC coding Phase 1 finished and I passed first evaluation. I received some honest feedback from my mentor Naveen. First week I finished my some of my pending work in first phase. Upgraded IGitt in GitMate to fetch latest commits made my me, which will be needed for writing plugins. Then my PR on "Add Fixes vs Closes checking plugin" got merged. Comment by that plugin will be like this- Second Week For completing squash plugin, I have completed writing code for executing squash commands as required in mr-rebaser repository, also I submitted a PR for executing squash plugin in GitMate. Only a demo was required to complete that plugin. I started working on plugin called "Auto assign issue based on commit mention in PR", i.e if an unassigned issue is mentioned with keyword(Fixes, Closes) in commit message of the PR and there is no CI failure in the PR, then issue will assigned to PR author, else if an assigned issu
Read more

GSoC 2018 journey

-
Image
What is GSoC? Google Summer of Code (GSoC) is an online, international program designed to encourage university student participation in open source software development. Students work for an open source software organization, and earn a stipend for successfully completing the project. If you want to know more about GSoC, click  here . How it all started? I joined a student club called  FOSS@AMRITA  in Amrita University , where a group of students work on various open source projects helping each other. I got to know about GSoC from the club itself, most of the previous year GSoC students from our college were members of the club. I was motivated by seeing them and started learning coding, staying in the lab after my college hours. Why I was attracted to GSoC is for real world experience, to prove myself that I can do something and for swag, stipend too. Why coala? Choosing an organization from previous year GSoC orgs was a hard one. Initially, I chose  Joomla  a
Read more

GSoC Coding Phase 3 ends

-
Coding Phase 3 Last phase of GSoC period is completed. In this phase, I finished all the work which was pending in the previous phases. Week 3: I implemented squash command in GitMate, to squash all commits in a pull request into a single commit with defined commit message. This feature was supposed to implemented in the first phase, but there were some issues when giving multi line commit message and when there is merge commit, so I implemented a command to squash last 'n' number of commits instead of squashing given set of commits. Also, my cEP got merged, after many amendments. Week 4: I worked on adding assign request command which assigns and unassigns an issue to a user who requests for assignment or unassignment. Also, a user must satisfy all the eligibility conditions to get assigned to the issue. This one involved with writing many test cases. Check my pull request here . I started working on merging all pull request review plugins into
Read more