Issue
Contribution records
Contributors

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

Give credit to everyone
nedjo
kkaefer
eaton
webchick organization(s): Acquia
sanketmedhi
kazim59
drumm
JirkaRybka
pancho
yoroy
amc
mcrittenden
johnalbin
Bojhan volunteering
jensimmons
dodorama
bojanz
mitchell
berdir
xano
larowlan organization(s): PreviousNext
mitokens volunteering
jhedstrom organization(s): Phase2
yesct
jibran volunteering
eojthebrave organization(s): Drupalize.Me
sylus
ressa volunteering
dsnopek
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
rachel_norfolk organization(s): Open Development Ltd customer(s): Horizons Unlimited
andypost volunteering organization(s): Skilld
kjay
lauriii volunteering organization(s): Druid
ok_lyndsey volunteering
Stefan Nagtegaal
killes@www.drop.org
gábor hojtsy organization(s): Acquia
boris mann
eli-t
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.