Contribution records
Contributors

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

Give credit to everyone
s3b0un3t S3b0uN3t volunteering
marciaibanez marciaibanez organization(s): CI&T
mglaman mglaman organization(s): Acquia
nkoporec nkoporec
bircher bircher volunteering organization(s): Nuvole
acbramley acbramley organization(s): PreviousNext customer(s): Service NSW
Guilherme Rabelo GuilhermeRabelo organization(s): CI&T
kristen pol kepol organization(s): Itty Bitty Byte customer(s): Salsa Digital
kim.pepper kimpepper organization(s): PreviousNext
rajab natshah RajabNatshah organization(s): Vardot customer(s): Vardot
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.