Contribution records
Contributors

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

Give credit to everyone
alcroito placinta
nlambert nlambert volunteering
hydra Hydra
juliakoelsch Spry_Julia organization(s): Spry Digital, LLC
joelstein joelstein
proteo Proteo volunteering
kyletaylored KyleTaylored volunteering organization(s): LevelTen Interactive
mrtndlmt mrtndlmt
lmeurs lmeurs
jimmyko jimmyko volunteering
matthiasm11 matthiasm11 organization(s): MM-Experience
idebr idebr organization(s): ezCompany
jollysolutions jollysolutions
mikeytown2 mikeytown2
jatorresdev jatorresdev
donaldinou donaldinou volunteering
philsward philsward
NerOcrO nerocro organization(s): Axess Open Web Services
joelpittet joelpittet volunteering
das-peter daspeter
vancec Coletain volunteering
lunk rat LunkRat
tessa bakker TessaBakker organization(s): ezCompany
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.