Issue
Contribution records
Contributors

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

Give credit to everyone
g4mbini organization(s): Alliance of Digital Builders (AODB), Dropteam
alanburke organization(s): Annertech
chetansonawane volunteering organization(s): QED42
dhansen organization(s): Sevaa Group
echechulina organization(s): Kanopi Studios
goz organization(s): Iosan
grimreaper organization(s): Smile
laetitia_al organization(s): Smile
maboy organization(s): Smile
mh_nichts
mr_scumbag organization(s): Code Journeymen customer(s): Code Journeymen
nicoloye volunteering
nod_ organization(s): Très Bien Tech
osman_seferov
pdureau volunteering
raluelrusu volunteering
sharique volunteering customer(s): Drupal India Association
vzsigmond organization(s): Annertech
christian.wiedemann organization(s): keytec GmbH & Co. KG
rajab natshah organization(s): Vardot customer(s): Vardot
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.