Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
sardiwal
larowlan organization(s): PreviousNext
szeidler organization(s): Ramsalt Lab
yonailo
escilm2
jsank
imclean organization(s): Digital Ink
tjtj
ballaboidi volunteering
amannim volunteering
jnimchuk
tolstoydotcom volunteering
azovsky
lapurddrupal volunteering
flyke
codesmith organization(s): Mission Web Works
lauriii organization(s): Acquia
ricardochefigueroa
mupsi volunteering
ikke
dalin organization(s): Four Kitchens customer(s): American Federation of Teachers
rahaf albawab
cangurin limpiezas volunteering organization(s): Cangurin limpiezas Zaragoza
santhosh@21 volunteering
geek-merlin organization(s): Geeks4Change, MachbarMacher
smustgrave organization(s): Mobomo
quietone volunteering
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.