Contribution records
Contributors

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

Give credit to everyone
NadiaFaucon NadiaFaucon
leslieg lglynn2299 organization(s): Redfin Solutions, LLC
aaronmchale AaronMcHale
bsnodgrass bsnodgrass organization(s): net2Community, Inc.
chrisfromredfin chrisfromredfin organization(s): Redfin Solutions, LLC
drumm drumm organization(s): Drupal Association
dww dww organization(s): TEN7
hestenet hestenet organization(s): Drupal Association
portulaca portulaca
volkswagenchick volkswagenchick organization(s): Red Hat
andrewozone andrewozone organization(s): Bounteous
bostonjillian bostonjillian
hildog hprager07
zebruh_divs zebruh_divs organization(s): Acquia
damienmckenna damienmckenna organization(s): Current
mandclu mandclu organization(s): Acquia
rajab natshah RajabNatshah organization(s): Vardot customer(s): Vardot
run fast think slow -lets4- lets4 volunteering
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.