Issue
Contribution records
Contributors

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

Give credit to everyone
cburschka
yched
jbrauer
treksler
aspilicious
ksenzee
David_Rothstein
catch
marcvangend
amateescu
nod_
kosilko
robloach
sun
kiphaas7
lomo
dasjo
webchick
lightsurge
osopolar volunteering
yonailo
anybody volunteering
pounard
giupenni
legovaer organization(s): The Reference
frederikvho organization(s): The Reference
klausi organization(s): jobiqo - job board technology
ApacheEx volunteering organization(s): Drupal Ukraine Community
sleitner
dsnopek customer(s): UC Berkeley Web Platform Services
ressa organization(s): Ardea
mcdruid volunteering organization(s): Acquia
mile23
fabianx volunteering organization(s): Tag1 Consulting, Inc.
izmeez
keith.smith
robin monks
lil-1
Everett Zufelt
damien tournoud
dave reid
wim leers
Tor Arne Thune
mot-k
jonathan.green
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.