Contribution records
Contributors

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

Give credit to everyone
borisson_ borisson_ volunteering organization(s): Calibrate
g4mbini G4MBINI organization(s): Actency , Alliance of Digital Builders (AODB), Dropteam, emerya, Trained People
nick_vh nickvh organization(s): Dropsolid
alexpott alexpott organization(s): Acro Commerce, Thunder
beram beram volunteering organization(s): Ekino
ekes ekes organization(s): Agile Collective customer(s): LocalGov Drupal
lauriii lauriii organization(s): Acquia
marcvangend marcvangend volunteering organization(s): ronder
pdureau pdureau volunteering
svdhout svdhout organization(s): Calibrate
GrimReaper-1 GrimReaper-1
gábor hojtsy goba organization(s): Acquia
wim leers wimleers organization(s): Acquia
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.