Issue
Contribution records
Contributors

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

Give credit to everyone
cilefen volunteering
finallylea
andypost volunteering organization(s): Skilld
peleccotur organization(s): Betawerk
stuchl4n3k organization(s): NetrixOne
bserem organization(s): Point Blank, SRM customer(s): Greek Drupal Community, Point Blank
znerol
lind101
jfurnas organization(s): Center for Educational Networking
alexpott organization(s): Acro Commerce, Thunder
fool2 organization(s): Spry Digital, LLC
tomsaw volunteering
jonmcl
davisben
quietone organization(s): PreviousNext
rpayanm organization(s): Agileana
xjm organization(s): Agileana, xjm
smustgrave organization(s): Mobomo
luenemann organization(s): FlexiFlow GmbH
fluidstack volunteering
ivnish
daniels____
ravi.shankar organization(s): OpenSense Labs
problue solutions
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.