Contribution records
Contributors

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

Give credit to everyone
munzirtaha munzirtaha volunteering
cchanana cchanana
trevorkjorlien trevorkjorlien volunteering organization(s): Floe design + technologies
mparker17 mparker17 organization(s): OpenConcept Consulting Inc.
lewisnyman lewisnyman organization(s): Mearra (formerly known as Wunder)
rudraram rudraram organization(s): Axelerant
fil00dl fil00dl organization(s): Skilld
jim005 jim005 organization(s): WebSenso
chipway chipway-drupal organization(s): Chipway
elchiconube elchiconube volunteering
rbrissaud rbrissaud
davidhernandez davidhernandez volunteering
bendev bendev organization(s): WebstanZ
catch catch
xjm xjm organization(s): Acquia
webchick webchick organization(s): Acquia
rachel_norfolk rachel_norfolk organization(s): Cambridge University Press & Assessment
manjit.singh Manjit.Singh organization(s): Material
emma.maria emma.maria
nicolas@webstanz.be nicolas-at-webstanz.be
meenakshi.r meenakshi.r volunteering organization(s): Material
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.