Contribution records
Contributors

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

Give credit to everyone
josmera01 josmera01 organization(s): Globant
dagmar dagmar organization(s): Globant
megachriz megachriz volunteering organization(s): WebCoo
RKopacz RKopacz volunteering
tedwyer tedwyer
ByteJunk ByteJunk volunteering
huida huida
smartparty smartparty
kumkum29 kumkum29
memoday memoday
caldenjacobs caldenjacobs
kclarkson kclarkson volunteering organization(s): Kennesaw State University
jwineichen jwineichen volunteering
topplestack Topplestack
dhayanandan_k dhayanandan_k
irinaz irinaz volunteering
sambathbask sambathbask
thomasmurphy thomasmurphy organization(s): Xequals
dman dman volunteering
hughmccracken hughmccracken volunteering
dchatry Rivals volunteering
trevorbradley TrevorBradley
Daniel Schaefer Daniel Schaefer
Jeff Burnz jmburnz
Ali Webb Ali Webb
Lea Sky Lea Sky volunteering
max-kuzomko max-kuzomko customer(s): Fibonacci Web Studio
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.