Issue
Contribution records
Contributors

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

Give credit to everyone
damienmckenna organization(s): Current
trobey volunteering
andypost volunteering organization(s): Skilld
pwolanin volunteering organization(s): SciShield
tobiasb volunteering
taran2l organization(s): Drupal Ukraine Community, Lemberg Solutions
HaiNguyen007
larowlan organization(s): PreviousNext
jofitz organization(s): ComputerMinds
alexpott organization(s): Thunder
dawehner organization(s): Chapter Three (acquired by Kanopi Studios)
tucho organization(s): gcoop Cooperativa de Software Libre
tstoeckler organization(s): bio.logis Genetic Information Management GmbH
phenaproxima organization(s): Acquia
nickdickinsonwilde volunteering organization(s): BriarMoon Design
-enzo- organization(s): weKnow Inc customer(s): Department of Premier and Cabinet - Victoria, Australia
rajab natshah organization(s): Vardot
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.