Contribution records
Contributors

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

Give credit to everyone
cilefen cilefen volunteering
daggerhart daggerhart organization(s): Hook 42
nkoporec nkoporec volunteering organization(s): Agiledrop - Your Trusted Drupal Teammates
tatarbj tatarbj
nerdstein nerdstein volunteering organization(s): Hook 42
esolitos esolitos organization(s): Ramsalt Lab
jeroent JeroenT organization(s): iO
mcdruid mcdruid organization(s): Acquia
d0t15t dotist volunteering
jeroen.b jeroen.b organization(s): .VDMi/
david.hughes david.hughes organization(s): Cancer Research UK
kim.pepper kimpepper organization(s): PreviousNext
kristen pol kepol organization(s): Salsa Digital customer(s): govCMS (Australian Government Department of Finance)
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.