Issue
Contribution records
Forks management
Issue edit
Contributors

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

Give credit to everyone
ericpugh organization(s): Smithsonian Institution
empesan
haza organization(s): Happyculture
mathysp organization(s): Dazzle
jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
borisson_ volunteering
u_tiwari
wturrell volunteering
interdruper organization(s): Interdruper
pcate
mattdanger
anmolgoyal74 organization(s): OpenSense Labs customer(s): DrupalFit
adityasingh volunteering organization(s): Material customer(s): Drupal India Association
tstoeckler volunteering
quietone organization(s): PreviousNext
balagan organization(s): Gizra
ankithashetty volunteering organization(s): Specbee customer(s): Drupal India Association
poker10 organization(s): ActivIT s.r.o.
smustgrave organization(s): Mobomo
thefancywizard organization(s): Slalom
rakesh.gectcr volunteering organization(s): Valuebound
mr.baileys
kevin.dutra organization(s): Workday, Inc.
abhijith s volunteering organization(s): Zyxware Technologies
liam morland organization(s): OpenPlus, Scouting Waterloo Region
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.