Issue
Contribution records
Contributors

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

Give credit to everyone
sweetchuck volunteering organization(s): Cheppers
cilefen organization(s): Institute for Advanced Study
vitaliyb98 organization(s): Internetdevels
martin107 volunteering
ankitjain28may volunteering organization(s): Google Summer of Code
borisson_ volunteering
quietone volunteering organization(s): PreviousNext
sutharsan organization(s): ronder
heykarthikwithu volunteering organization(s): Material customer(s): Drupal India Association
beatrizrodrigues organization(s): CI&T
daffie organization(s): Finalist
cosmicdreams volunteering
lucienchalom organization(s): CI&T
WagnerMelo organization(s): CI&T
bbrala volunteering organization(s): SWIS
sophiavs organization(s): CI&T
longwave organization(s): Full Fat Things
catch organization(s): Third and Grove
alexpott organization(s): Acro Commerce, Thunder
ravi.shankar organization(s): OpenSense Labs
bruno.bicudo organization(s): CI&T
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.