Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
jeet09
yesct
idebr
RavindraSingh
mglaman
alimac
David_Rothstein
Bojhan
nod_ organization(s): Smile
phillamb168 volunteering
xjm organization(s): Acquia, xjm
cilefen
mgifford organization(s): OpenConcept Consulting Inc.
prasad_gogate organization(s): Acquia
shamsher_alam volunteering
alexpott organization(s): Acro Commerce, Thunder
AmolB
eelkeblok organization(s): iO
shaktik volunteering
mkolar organization(s): Ciklum Western Europe customer(s): BurdaForward
larowlan organization(s): PreviousNext
DonAtt volunteering
auseidon986 volunteering
dimilias customer(s): European Commission and European Union Institutions, Agencies and Bodies
raffaelj
sagarmohite0031 organization(s): QED42 customer(s): Drupal India Association
rkoller
smustgrave organization(s): Mobomo
catch organization(s): Third and Grove
prudloff organization(s): Insite
Adam Neutrik
rob c
gábor hojtsy organization(s): Acquia
nitin shrivastava organization(s): OpenSense Labs
jan kellermann organization(s): werk21
prashant.c volunteering organization(s): QED42 customer(s): Drupal India Association
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.