Issue
Contribution records
The link is currently not reachable and cannot be changed. The data shown below might be obsolete.
Contributors

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

Give credit to everyone
mmrares
jrockowitz volunteering organization(s): The Big Blue House
michielkenis volunteering
paulvandenburg volunteering organization(s): ezCompany, iO
leksat organization(s): Amazee Labs
catch organization(s): Third and Grove
mpp volunteering organization(s): AmeXio Fuse customer(s): District09
renguer0 volunteering
shubhangi1995
guptahemant volunteering organization(s): QED42
andypost volunteering organization(s): Skilld
pavelculacov
gobinathm volunteering
spokje volunteering
anmolgoyal74 organization(s): OpenSense Labs customer(s): DrupalFit
nevergone volunteering
vodde83 organization(s): Anvil
thomjjames organization(s): Frontkom
michel.g organization(s): Randstad Digital customer(s): Government of Flanders
martijn de wit organization(s): Ablerz
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.