Contribution records
Contributors

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

Give credit to everyone
josephdpurcell josephdpurcell organization(s): Bounteous
waverate waverate
zeuty zeuty volunteering
berdir berdir organization(s): MD Systems GmbH
robpowell robpowell organization(s): Current
katherined katherined
phenaproxima phenaproxima organization(s): Acquia
thalles thallesvf organization(s): CI&T
pranit84 pranitjha volunteering organization(s): Acquia
andreyjan andreyjan organization(s): JAKALA (formerly FFW)
amitgoyal amitgoyal organization(s): Acquia
robertoperuzzo robertoperuzzo volunteering organization(s): Studio Aqua
malaynayak malaynayak volunteering organization(s): Acquia customer(s): Drupal India Association
fm_ fm_ organization(s): hiberus
damienmckenna damienmckenna organization(s): Current
grasmash madmatter23
hugovk hugovk organization(s): Digia customer(s): Yle - Finnish Broadcasting Company
sergiu stici sergiustici organization(s): JAKALA (formerly FFW)
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.