Contribution records
Contributors

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

Give credit to everyone
imclean imclean
78doog 78doog
danhooker danhooker
sylus sylus
kenorb kenorb
roam2345 jucallme
arnoldbird arnoldbird
dawehner dereine volunteering
xbrianx xbrianx
mrharolda haroldmadcap
guguss GuGuss
lmeurs lmeurs
joelpittet joelpittet
recrit recrit
JvE JvE organization(s): One Shoe
danepowell danepowell organization(s): Acquia
rooby rooby
hkovacs hkovacs volunteering
GoddamnNoise GoddamnNoise organization(s): Karakana Factoría TIC
amjad1233 amjad1233 organization(s): Web Prophets
damienmckenna damienmckenna organization(s): Current
kporras07 kporras07 organization(s): Manatí
ljgra ljgra
ckng ckng organization(s): O8
dalejung dalejung
kerasai bmoresafety20
das-peter daspeter organization(s): Cando
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.