Issue
Contribution records
Contributors

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

Give credit to everyone
damienmckenna organization(s): Current
jofitz organization(s): ComputerMinds
mikeryan organization(s): Virtuoso Performance
Benia
csedax90
tedfordgif organization(s): WebFirst, Inc.
matthieuscarset volunteering organization(s): Appnovation customer(s): Appnovation
mglaman organization(s): Centarro
pobster organization(s): ArcadeGeek LTD customer(s): Rackspace
pobtastic organization(s): ArcadeGeek LTD
pcranston
WidgetsBurritos organization(s): Rackspace
benjifisher organization(s): Isovera customer(s): Pegasystems
heddn organization(s): MTech, LLC
socketwench organization(s): TEN7
marvil07 organization(s): Isovera
PierreRicci
ricardochefigueroa
marcelovani organization(s): Dennis
floown
papagrande volunteering
drupalninja99 organization(s): Current
oliverpolden
john_b
cruno
ccarrascal
steven jones organization(s): ComputerMinds
a.milkovsky organization(s): Styria Digital Services
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.