Updates :

• All patches got merged into the main codebase. The work could be traced as here : Merged Patches
• The new feature got released in Git revision 2.33 , see the detailed usuage as here : Skip to new –fixup options : amend and reword
• Checkout our blog post of Outreachy Interenship Experiences : “Technology internships meet open source in Outreachy”

Received reviews on the previous patch series and continued working on the Implementation of "drop!" commit.

Last week I spent on stitching up the loose points in the prepared patches of “amend!” commit (workbranch) and finally sent it to the mailing list. After that also started with the second part of project i.e to Implement the “drop!” commit.

U TURN in the project and worked on further improvements required in the previous patch series.

Last week I spent on preparing the patch series, for the implementation of amend! commit (work-branch) and about to send it on the mailing list.

Last week was spent debugging the patch series, solving bug, addressing the code reviews and also doing some corrections in implementation of amend! commit.

Received reviews on the patch series sent last week to Git mailing list and also discussed regarding the implementation of next subtask.

Writing CLEAN CODE - CLEAN PATCHES - that are easily readable and maintainable is also an essential part. So, this week is spent mostly on fixing up the commits, commit messages, making preparatory/clean-up patches and debugging for more changes.

I started with, finding the answers of what happens when we run git rebase -i ? How does the code work after we edit the git-rebase-todo ?

Working on git using git. And it’s true that we can’t just avoid the conflicts. Although, git makes the merging or integration of code from different branches very easy and handles itself but there are many situations in which it results in merge conflicts and at that time it is required to be solved manually.

My first task in the project is to Implement the reword! commit in the git interactive rebase. This would be an alternative to the fixup! and squash! commit which would allow the user to edit the commit (either commit message or content or both) when they create a reword! commit rather than when they rebase. And for the coming weeks I will be working on this task.

All it started with Open Source. I always wanted to be an active open source contributor and believe that the best way to improve skills is by contributing to open source projects.