Contribution records
Contributors

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

Give credit to everyone
hestenet hestenet organization(s): Drupal Association
b_man B_man organization(s): Drupal Association
andrewozone andrewozone organization(s): Bounteous
bsnodgrass bsnodgrass organization(s): net2Community, Inc.
leslieg lglynn2299 organization(s): Redfin Solutions, LLC
rlnorthcutt rlnorthcutt volunteering organization(s): Acquia
rukayya rukayya organization(s): QED42 customer(s): Drupal Association
shaal shaal volunteering organization(s): Phase2
thejimbirch thejimbirch organization(s): Kanopi Studios
volkswagenchick volkswagenchick organization(s): Kanopi Studios
zviryatko zviryatko volunteering customer(s): Nuvole
bostonjillian bostonjillian
jonmeck jonmeck organization(s): Bounteous
guptahemant guptahemant volunteering organization(s): QED42
rajab natshah RajabNatshah organization(s): Vardot customer(s): Vardot
tim.plunkett tim.plunkett organization(s): Acquia
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.