Contribution records
Contributors

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

Give credit to everyone
birdmanx35 birdmanx35
coltrane coltrane
karschsp karschsp
catch catch
gaele gaele
berenddeboer berend
bergco bergco
eigentor eigentor
seutje seutje
Bojhan bojhan
heather heather
yoroy yoroy
dries dries
MichaelCole michaelcole
redndahead redndahead
axyjo axyjo
arianek arianek
bluepanther3 bluepanther3
cosmicdreams cosmicdreams
quietone quietone organization(s): PreviousNext
keith.smith keithsmith
willhall-dupe willhall-dupe
adrianrf@gmail.com adrianrf
greg.harvey greg.harvey
amit.drupal amit.drupal volunteering organization(s): gai Technologies Pvt Ltd customer(s): gai Technologies Pvt Ltd
gaurav.kapoor gaurav.kapoor organization(s): OpenSense Labs
abhijith s AbhijithS volunteering organization(s): Zyxware Technologies
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.