Contribution records
Contributors

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

Give credit to everyone
vinmayiswamy VinmayiSwamy volunteering organization(s): Material customer(s): Drupal India Association
smustgrave smustgrave organization(s): Mobomo
gauravvvv Gauravmahlawat organization(s): Axelerant customer(s): Drupal India Association
mradcliffe mradcliffe volunteering
xjm xjm organization(s): HeroDevs, xjm
kyle.davis kyledaviswx volunteering
jvest jvest volunteering
ericrubino ericrubino volunteering
bnjmnm bnjmnm organization(s): Acquia
utkarsh_33 Utkarsh_33 volunteering organization(s): Acquia
quietone quietone organization(s): PreviousNext
nod_ nod_ organization(s): Très Bien Tech customer(s): OPTASY, Palantir.net, Vardot
sdhruvi5142 sdhruvi5142 organization(s): QED42
idebr idebr organization(s): iO
emb03 emb03
juanolalla juanolalla organization(s): Peak Digital, LLC
msantin0 msantin0
mithun s Mithun_S customer(s): QED42
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.