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
ccjjmartin volunteering
grimreaper organization(s): Smile
just_like_good_vibes volunteering
kerrymick organization(s): Kanopi Studios
laetitia_al organization(s): Smile
maboy organization(s): Smile
mherchel organization(s): Dripyard
mogtofu33 volunteering organization(s): Beyris
nkarhoff organization(s): Kanopi Studios
nod_ organization(s): Très Bien Tech
pdureau volunteering
sharique volunteering customer(s): Drupal India Association
vdanielpop organization(s): PitechPlus
vmaucorps organization(s): Smile
walli
christian.wiedemann organization(s): keytec GmbH & Co. KG
fboulanger
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.