Contribution records
Contributors

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

Give credit to everyone
dczepierga dczepierga
nidhijsen nidhijsen
bzrudi bzrudi
Petrica PetricaB
carvalhar carvalhar
nymo nymo
stephenrobinson SangersDrupalDude
anil_89 anil_89
jcisio jcisio
dariusa dariusa
cilefen cilefen
xuxizh xuxizh
merzikain merzikain
jnavane jnavane
phponwebsites phponwebsites
scaballeronavia scaballeronavia volunteering
millisaeubanks millisaeubanks
jeff.maes jeff.maes
bel.inna bel.inna
Navneet.Chauhan Navneet.Chauhan
nicholas.alipaz nicholasalipaz
谢艳 yxie
thaistore thaistore
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.