Issue
Contribution records
Contributors

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

Give credit to everyone
Iriina
philipnorton42 organization(s): Access (now GAIN)
pdjohnson organization(s): CTI Digital
rachel_norfolk
vijaycs85 volunteering organization(s): Solathat, TATA Consultancy Services customer(s): Pfizer, Inc.
cferthorney volunteering
h2cm volunteering
rattusrattus organization(s): Agile Collective
alexmoreno organization(s): Acquia
dawehner volunteering
justafish organization(s): Lullabot customer(s): DocuSign
yautja_cetanu
gambry organization(s): manifesto
waliur
crispin
ipwa organization(s): manifesto
eli-t
john cook organization(s): Creode
emma.maria organization(s): TES Global
Phil Wolstenholme volunteering organization(s): CTI Digital
Not Real
rakesh.gectcr 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.