Contribution records
Contributors

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

Give credit to everyone
marcoscano marcoscano volunteering organization(s): Lullabot customer(s): Acquia
rogerpfaff rogerpfaff organization(s): Reinblau
webflo webflo organization(s): UEBERBIT GmbH
dhruveshdtripathi DhruveshTripathi organization(s): DevsAdda
naveenvalecha naveenvalecha volunteering
berdir berdir organization(s): MD Systems GmbH
phenaproxima phenaproxima organization(s): Acquia
seanb seanB
amateescu amateescu customer(s): Pfizer, Inc.
parijke parijke
tacituseu tacituseu
Bojhan bojhan volunteering
vijaycs85 vijaycs85 volunteering
xjm xjm organization(s): Acquia, xjm
yoroy yoroy organization(s): Roy Scholten
benjifisher benjifisher organization(s): Isovera
larowlan larowlan organization(s): PreviousNext
joachim joachim
webchick webchick organization(s): Acquia
rootwork rootwork volunteering
gábor hojtsy goba organization(s): Acquia
wim leers wimleers organization(s): Acquia
martijn de wit martijndewit organization(s): Ablerz
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.