Issue
Contribution records
Contributors

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

Give credit to everyone
xano organization(s): Druid, My name is Bart
Crell
twistor volunteering
larowlan organization(s): PreviousNext
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
fabianx volunteering organization(s): Tag1 Consulting, Inc.
znerol
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
effulgentsia
tibbsa
jibran volunteering
xjm organization(s): Acquia
pol volunteering
mile23 volunteering
andypost volunteering organization(s): Skilld
chx volunteering
catch organization(s): Third and Grove
joelpittet
jofitz organization(s): ComputerMinds
jonathan1055 volunteering
markhalliwell organization(s): Tag1 Consulting, Inc.
kim.pepper organization(s): PreviousNext
tim.plunkett
wim leers organization(s): Acquia
gábor hojtsy organization(s): Acquia
claudiu.cristea organization(s): Webikon
pritishkumar organization(s): OpenSense Labs
rob c
hass
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.