Contribution records
Contributors

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

Give credit to everyone
rupertj rupertj
kiwimind kiwimind
webroru aa2007
rogermcallen rogermcallen
Patricec Patricec
savingstrangers savingstrangers
duaelfr DuaelFr
ponies ponies
bradhawkins bradhawkins
andyf andy
nandotinoco nandotinoco
scarr scarr
tbenice tbenice
ioanmar ioanma
divan divan
joecanti joecanti
shaneonabike ShaneOnABike
torgospizza torgospizza
nodecode nodecode
svouthi svouthi
DrMicky DrMicky
chrisNtampa chrisrocha
summit summit
zmove zmove
deggertsen deggertsen
calmforce calmforce
blueblade blueblade
macman911 macman911
jpmelguizo jpmelguizo
Exigo Exigo
perignon Perignon
rcodina rcodina
lalbright lalbright
ñull com2
Jason Dean pushka
muhammad.tanweer muhammad.tanweer
la.carvalho la.carvalho
star-szr star-szr
Tor Arne Thune torthu
Open Pixel Open Pixel
drupal4u.org drupal4u.org
das-peter daspeter
Jeremy Scott Jeremy Scott
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.