Issue
Contribution records
Contributors

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

Give credit to everyone
jaykandari volunteering organization(s): QED42
ayesh
Neo13
sjerdo volunteering organization(s): Synetic
andypost volunteering organization(s): Skilld
vprocessor organization(s): Skilld
piggito volunteering organization(s): Skilld
oriol_e9g organization(s): Diputació de Barcelona
David_Rothstein volunteering
mikeytown2
delta volunteering
bkosborne organization(s): Princeton University
yogeshmpawar organization(s): QED42
fabianx organization(s): Tag1 Consulting, Inc.
amme
pol organization(s): Arhs customer(s): European Commission and European Union Institutions, Agencies and Bodies
Mixologic organization(s): Drupal Association
devu_divya
ljndit
mustanggb
magmatic volunteering
siramsay volunteering
matas.k
damienmckenna organization(s): Current
dks786
joseph.olstad
s@ilor
anonymous coward
bart lambert
jacob.embree organization(s): St. Louis Integration
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.