Contribution records
Contributors

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

Give credit to everyone
stella stella organization(s): Annertech
bojanz bojanz organization(s): Centarro
dpopdan dpopdan volunteering
gargsuchi gargsuchi organization(s): Salsa Digital customer(s): govCMS (Australian Government Department of Finance)
matjes matjes
mon_franco mon_franco
paych paych organization(s): ADCI Solutions
pcambra pcambra organization(s): Cambrico
rosinegrean prics organization(s): PitechPlus
rvolk rvolk volunteering organization(s): Drupal e.V.
brenv brenv organization(s): Annertech
gambry gambry organization(s): manifesto
juliapradel juliapradel organization(s): Thunder
katzilla katzilla organization(s): Reinblau
rpsu rpsu organization(s): Exove
tsega tsega organization(s): Axelerant
piyushpoddar piyushpoddar volunteering organization(s): Axelerant
rachel_norfolk rachel_norfolk organization(s): Drupal Association
imre gmelig meijling imre_gmelig_meijling
rakesh.gectcr rakeshjames volunteering customer(s): Access (now GAIN)
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.