Issue
Contribution records
Contributors

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

Give credit to everyone
vijaycs85 volunteering organization(s): Solathat, TATA Consultancy Services customer(s): Pfizer, Inc.
tatarbj organization(s): Petend customer(s): European Commission and European Union Institutions, Agencies and Bodies
mahalingam_cs organization(s): TATA Consultancy Services
valthebald
David_Rothstein volunteering
klausi organization(s): jobiqo - job board technology
oadaeh organization(s): Hook 42
pandaski organization(s): govCMS (Australian Government Department of Finance)
mustanggb
megachriz organization(s): WebCoo
poker10 organization(s): ActivIT s.r.o.
mcdruid organization(s): Acquia
joseph.olstad
rob c
Michael-IDA organization(s): Internet Design Alliance
nagy.balint organization(s): Webbtik.io
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.