Contribution records
Draft
Contributors

Granted credits are reviewed by maintainers. Learn more about granting credit.

Give credit to everyone
uNeedStuff uNeedStuff
Shai Shai
Bojhan bojhan
David_Rothstein drothstein
marcingy marcingy
colan colan
yoroy yoroy
sun sun
xjm xjm volunteering
pancho pancho
hansyg hansyg
frob frob organization(s): Clarity Innovations, Inc.
rkjha rkjha
larowlan larowlan organization(s): PreviousNext
tstoeckler tstoeckler
catch catch
yched yched
heddn lucashedding
jbloomfield jbloomfield
sidharrell sidharrell
skh skh
arunkumark arunkumark
webchick webchick organization(s): Acquia
xem8vfdh xeM8VfDh
smustgrave smustgrave organization(s): Mobomo
Everett Zufelt everettz
mike stewart mdrmike
tim.plunkett tim.plunkett
Patrick Storey Patrick_Storey volunteering organization(s): Hook 42
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit
  • task: A planned operational or maintenance change to the codebase

See the format of the Git commit message.

Copy and paste the message in the Merge UI screen or commit message. If needed, improve the title after you paste. The message follows conventional commits format.