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 a single review plugin. Plugins which were supposed to be merged are approver, ack and auto label pending review or wip. Review plugin would handle approved, work in progress, pending review labels. This feature still needs some design, because in the future many plugins may be adding review label, but merging it with review plugin just because of adding review label will be weird. I thought of declaring the label settings in the main review plugin and reuse them in every plugin, but my mentor Naveen suggested not to implement this method as it may lead to errors if we turn off review plugin, but want to implement other dependent plugin.

 I finished almost all the work of my project except the merging review plugins thing. Code submission starts today and I will know the result on August 22nd.

Comments

Post a Comment

Popular posts from this blog

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 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 Coding Phase 2 ends

-
Coding Phase 2 Coding phase 2 has come to an end, I worked almost everyday in this phase, I finished lots of work including the one which was left over in phase 1. Though I tried to complete all the tasks as planned, there were a couple of issues left over which would take some extra time. Week 3 : I worked on "Adding Team class" in IGitt, which was a little tricky one because GitLab doesn't have teams. So, assuming GitLab groups(which actually represent organization) as teams was a workaround for the problem. Then I added a feature "Auto assign issues based on commit mention in PR". When any user opens a PR(pull request) and mentions issues, which are being closed or fixed, in commit message, GitMate automatically assigns PR author to the mentioned unassigned issues and if anyone else is assigned to mentioned issues, GitMate will inform the user to work on other issues. You can check out my merged MR here . Week 4 : I made a PR on adding `mergea
Read more