Issue
Contribution records
Contributors

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

Give credit to everyone
timodwhit
eclipsegc organization(s): Acquia
nebel54 organization(s): OSCE: Organization for Security and Co-operation in Europe
grantkruger
bkosborne organization(s): Princeton University
sam152 volunteering organization(s): PreviousNext
fago organization(s): drunomics
josephdpurcell organization(s): Bounteous
gnikolovski volunteering organization(s): Studio Present
eiriksm organization(s): Foreningen Drupal Norge, Ny Media AS, Violinist
larowlan organization(s): PreviousNext
acbramley organization(s): PreviousNext
shaal volunteering organization(s): Palantir.net customer(s): Tableau
xjm organization(s): Acquia
andypost volunteering organization(s): Skilld
tim.plunkett organization(s): Acquia
morbus iff
Shishir Kumar
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.