Contribution records
Contributors

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

Give credit to everyone
duckydan duckydan
amandeep123 amandeep_lnwebworks organization(s): LN Webworks Private Limited
hjuarez20 harold20 volunteering organization(s): Stackgroup
robbymo robbymo organization(s): CTAC
vbouchet vbouchet organization(s): Acquia
idebr idebr organization(s): iO
roderik roderik organization(s): drunomics
dpi dpi volunteering organization(s): PreviousNext
dydave DYdave organization(s): Code Enigma
golubovicm golubovicm organization(s): drunomics
wim leers wimleers organization(s): Acquia
gábor hojtsy goba
nevergone nevergone
tomefa tomefa
itamair itamair volunteering
joelpittet joelpittet organization(s): The University of British Columbia
Git commit message
Commit types
  • 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

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.