Issue
Contribution records
Contributors

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

Give credit to everyone
dshaw
pancho
ruharen
theborg
cburschka
scoutbaker
robloach
babbage
JamieR
mfb
GregoryHeller
dries
kprmca
jcruz
perceptum
vm
mrfelton
carlos8f
benone
JaredAM
coyotemojo
pazzypunk
perke
c960657
shyam541
guypaddock
lukebrooker
cyberwolf
glitz
theodorosploumis
g000fy
frankfarm
gdud
pillarsdotnet
drupal_was_my_past
trzczy0
inkage
bismigalis
olamaekle
naxoc
xjm
sun
penyaskito
e0ipso
catch
geerlingguy
David_Rothstein
ogomez78
vasi1186
jochenf
jcisio organization(s): Axess Open Web Services
sokru volunteering
alexpott
gábor hojtsy
damien tournoud
matt v.
dave reid
Gabriel R.
Daniel Norton
lars toomre
ryan.ryan
andrew answer volunteering
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.