Issue
Contribution records
Contributors

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

Give credit to everyone
dasha_v
doublejosh
David_Rothstein volunteering
dagmar organization(s): Globant
thomasdbcklr organization(s): Dropsolid
falc0 organization(s): Dropsolid
benjifisher organization(s): Isovera
sgarrahy
mahalingam_cs organization(s): TATA Consultancy Services
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
pk188 organization(s): OpenSense Labs
jackpelorus volunteering organization(s): Globant
wesleydv organization(s): District09
xjm organization(s): Acquia
chaseontheweb
ralphvdhoudt organization(s): ezCompany
dpovshed volunteering
nico.knaepen organization(s): Logic in Motion customer(s): Colruyt Group Services
c.nish2k3 volunteering
john cook organization(s): Creode
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.