Issue
Contribution records
Contributors

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

Give credit to everyone
wells volunteering organization(s): Cascade PBS
duaelfr volunteering organization(s): Happyculture
sker101 volunteering
msuthars volunteering organization(s): CodeDuck customer(s): Drupal India Association
daften organization(s): Dropsolid
prudloff organization(s): Insite
saidatom organization(s): Squarebit customer(s): European Commission and European Union Institutions, Agencies and Bodies
alorenc organization(s): European Commission and European Union Institutions, Agencies and Bodies
percoction
timohuisman organization(s): SWIS
hkirsman
sokru volunteering
quotientix
joelpittet organization(s): The University of British Columbia
tijsdeboeck organization(s): Open Up Media
bbrala volunteering organization(s): SWIS
gaëlg organization(s): Insite
stefan lehmann organization(s): Eighty Options
wahavi
nsciacca
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.