Issue
Contribution records
Contributors

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

Give credit to everyone
catch organization(s): Third and Grove
duaelfr volunteering organization(s): Happyculture
Crell organization(s): Palantir.net
dawehner
acrosman volunteering organization(s): Cyberwoven
IRONFELIX
chi
kovtunos volunteering
pingwin4eg
alexpott organization(s): Thunder
pawel_r
karenann volunteering
sankarprakash
andypost volunteering organization(s): Skilld
pandaski organization(s): govCMS (Australian Government Department of Finance)
lauriii organization(s): Acquia
larowlan organization(s): PreviousNext
wim leers organization(s): Acquia
Pascal- organization(s): Open Up Media
ruslan piskarov volunteering
mr.baileys organization(s): SQLI - Belgium
krzysztof domański organization(s): abventor
OCTOGONE.dev
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.