Contribution records
Contributors

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

Give credit to everyone
gg24 gg24 volunteering organization(s): Salsa Digital
vladimiraus VladimirAus organization(s): Tomato Elephant Studio
andypost andypost volunteering organization(s): Skilld
dqd dqd volunteering organization(s): MAROQQO studios
kgaut Kgaut organization(s): Kgaut.NET
hswong3i hswong3i organization(s): PantaRei Design Limited (Hong Kong)
robcarr robcarr volunteering
phenaproxima phenaproxima organization(s): Acquia
pameeela pameeela organization(s): Technocrat
ankitv18 ankitv18 volunteering organization(s): Acquia
abhinavk AbhinavK organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
nebel54 Nebel54 organization(s): OSCE: Organization for Security and Co-operation in Europe
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.