Contribution records
Contributors

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

Give credit to everyone
volkswagenchick volkswagenchick organization(s): Hook 42
aimeerae aimeerae organization(s): Hook 42
jqtnguyen JQTNguyen organization(s): Hook 42
dani3lr0se Daniel_Rose organization(s): Hook 42
idcm idcm
mariohernandez mariohernandez volunteering
wesruv wesruv organization(s): Lullabot
jenlampton jenlampton organization(s): Jeneration Web Development customer(s): Backdrop CMS, Jeneration Web Development
dinarcon dinarcon organization(s): Agaric
mlncn mlncn volunteering organization(s): Agaric
zakiya zakiya organization(s): Chapter Three (acquired by Kanopi Studios)
Jaesin jaesin organization(s): Chapter Three (acquired by Kanopi Studios)
isramv isramv organization(s): Chapter Three (acquired by Kanopi Studios)
pirog pirog
wyee wyee organization(s): Chapter Three (acquired by Kanopi Studios)
thehuffman thehuffman organization(s): Current
areynolds areynolds organization(s): Tandem
kdassing kdassing
markie markie volunteering organization(s): Current
ultimike ultimike organization(s): DrupalEasy
chaz.chumley chazchumley
void-- void-- organization(s): Chapter Three (acquired by Kanopi Studios)
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.