Issue
Contribution records
Contributors

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

Give credit to everyone
alexpott organization(s): Thunder
berdir
andypost volunteering organization(s): Skilld
mlncn organization(s): Agaric customer(s): Drutopia
trevorbradley
pancho volunteering
bsztreha
extexan
phenaproxima organization(s): Acquia
douggreen volunteering
acbramley organization(s): PreviousNext customer(s): Service NSW
idebr organization(s): iO
joachim organization(s): Factorial.io
bceyssens organization(s): Nascom
jonathanshaw
akalam organization(s): Dropsolid
smustgrave organization(s): Mobomo
lauriii organization(s): Acquia
larowlan organization(s): PreviousNext
Webbeh organization(s): Georgia Institute of Technology
kristen pol organization(s): Hook 42
m.lebedev
tim.plunkett organization(s): Acquia
raman.b organization(s): OpenSense Labs
suresh prabhu parkala organization(s): Specbee
emircan erkul volunteering
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.