Contribution records
Draft
Contributors

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

Give credit to everyone
lilou lilou
stborchert stborchert
walkeroukor walkeroukor
dawehner dereine
sun sun
casey casey
xjm xjm
theunraveler theunraveler
andypost andypost volunteering organization(s): Skilld
HendrikM HendrikM
doublejosh doublejosh
franz franz
barraponto barraponto
Neo13 Neo13
tstoeckler tstoeckler
joelpittet joelpittet volunteering
yesct YesCT
lokapujya lokapujya organization(s): Babson College
xem8vfdh xeM8VfDh
lind101 lind101
edurenye edurenye organization(s): Digitalist
bnjmnm bnjmnm organization(s): Acquia
damienmckenna damienmckenna organization(s): Current
smustgrave smustgrave organization(s): Mobomo
wim leers wimleers
star-szr star-szr volunteering
tim.plunkett tim.plunkett
stefan.r stefan.r
eduardo morales alberti EduardoMoralesAlberti volunteering organization(s): Metadrop
apikongzad apikongzad
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.