Contribution records
Contributors

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

Give credit to everyone
pwolanin pwolanin organization(s): Acquia
xano Xano
Bojhan bojhan
jhedstrom jhedstrom organization(s): Phase2
jenmontgomery7 jenmontgomery7
mikeburrelljr mikeburrelljr volunteering
epophoto epo
xjm xjm organization(s): Acquia, xjm
sushantpaste ps_sushant organization(s): OSSeed Technologies
druprad pksingh1987 volunteering
dawehner dereine
srilakshmier srilakshmier organization(s): Valuebound customer(s): Valuebound
naveen433 naveen433 organization(s): Valuebound customer(s): Valuebound
andypost andypost volunteering organization(s): Skilld
benjifisher benjifisher organization(s): FRUITION
trackleft2 trackleft2 volunteering organization(s): The University of Arizona
quietone quietone organization(s): PreviousNext
smustgrave smustgrave organization(s): Mobomo
alvar0hurtad0 alvar0hurtad0 organization(s): Factorial.io
nod_ nod_ organization(s): Très Bien Tech customer(s): OpenSense Labs, OPTASY, Palantir.net, Vardot
Tor Arne Thune torthu
Patrick Storey Patrick_Storey volunteering organization(s): Hook 42
bs pavan BSPavan organization(s): Material
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.