As a [user] I need help with conventions

[blackfalcon]

General Support Request

As the Auro team is growing and more people are getting into the mix, the more the difference in naming conventions and commit messages can create momentary confusion.

Support request

It is healthy and time to discuss a naming convention for things like branches and update the standard for commit messages.

Possible Solution

When it comes to branch names, clarity and reference will always be preferred. On larger teams in the past, there has always been a convention that included the author's name and a reference to the issue they are solving. Having a brief description of the issue or a reference to the title is helpful too. An example I'd like to offer is,

dsande/i18nApi#110

or 

dsande/i18n/#110

I like this example as this quickly gives me the info I need. Also, as I am pulling other author's branches, this will help group branches between authors.

When it comes to commit messages, the format we already have is defined in the Conventional Commits section of the Auro site.

<type>[optional scope]: <description>

I would like to propose the following

1. The optional scope is not optional if there are more than one commits to a PR
2. The issue number is added to at least one comment in the PR

feat(fixed API): update fixed feature to accept arguments #905

Please offer your opinions in the comments below.

[blackfalcon]

The output of this should update the contributing guidelines for Auro as well as the newly proposed DoD document.