Issue
Contribution records
Contributors

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

Give credit to everyone
sandeepguntaka organization(s): Azri Solutions
danmuzyka organization(s): Phase2 customer(s): Workday, Inc.
rosk0 organization(s): Catalyst IT customer(s): Land Information New Zealand
jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
dafeder volunteering
seanb organization(s): Acquia
berdir organization(s): MD Systems GmbH
lobsterr organization(s): European Commission and European Union Institutions, Agencies and Bodies
kristiaanvandeneynde organization(s): Factorial.io, Tag1 Consulting, Inc.
kyuubi
wangshy organization(s): Northern Commerce
tstoeckler organization(s): resc.
heddn organization(s): MTech, LLC, Tag1 Consulting, Inc.
minoroffense organization(s): Coldfront Labs Inc.
joevagyok customer(s): European Commission and European Union Institutions, Agencies and Bodies
gorkagr organization(s): Erasmus Student Network
yakoub
catch organization(s): Third and Grove
vensires organization(s): E-Sepia Web Innovation
robin.ingelbrecht organization(s): EntityOne
dylan donkersgoed organization(s): Northern Commerce
moshe weitzman volunteering
ludo.r
geek-merlin organization(s): Geeks4Change, MachbarMacher
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.