Contribution records
Contributors

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

Give credit to everyone
effulgentsia effulgentsia organization(s): Acquia
aaronmchale AaronMcHale organization(s): The University of Edinburgh
aleksip aleksip
roberto_araya roberto_araya
brianperry backlineint organization(s): Bounteous
andypost andypost volunteering organization(s): Skilld
jwilson3 jwilson3
damienmckenna damienmckenna organization(s): Current
catch catch organization(s): Third and Grove
dww dww
bnjmnm bnjmnm organization(s): Acquia
jonathanshaw jonathanjfshaw
rfletcher73 rfletcher73
xjm xjm volunteering organization(s): xjm
quietone quietone volunteering organization(s): PreviousNext
ressa ressa organization(s): Ardea
rkoller rkoller
maxilein maxilein
gábor hojtsy goba organization(s): Acquia
tim.plunkett tim.plunkett organization(s): Acquia
lennard westerveld Cylon volunteering
kenton.r kenton.r
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.