# Improve your pull request workflow using pull-request-codecommit

on
Feb 23, 2022
in

In my previous blog post, I wrote why it is important to write good commit messages.
In this post I will highlight an example how this works in your advantage. Using an AWS CodeCommit repository.

## Working example

Alright, lets assume we have a project that uses a main branch. In combination with feature branches.
We want to add a feature to our project, so we create a branch called: feat/my-feature.

Let say we manage to get the feature working in a single commit. The commit message would look something like this:

By adding support for x we allow x users to adopt this tool in their workflow.

Issue: #123

Now it is time to create a pull request! I have created a tool called pull-request-codecommit.
This tool looks at the differences between the current branch. And the target branch and proposes a pull request message.

So if you want to create a pull request you type:

git pr

The default editor is opened. And in this editor you will see:

feat: add support for x (#123)

By adding support for x we allow x users to adopt this tool in their workflow.

Issue: #123

The first line will be used as the title and the rest as a description.
You can alter the message to your liking, but if you use a proper commit message this is spot on already.
When you save the proposal the pull request is created for you:

For convienience the link is displayed and the eventual message. When you open the link the pull request will look like this: