*BREAKING CHANGE*
* style(generate): changed generator to an HTML based one [WIP]
I added and set the HTML generator for resolving #154 (which works when testing manually but doesn't
when running the cli in dev mode).
fix#154
* refactor(generate): (re)moved files to keep it DRY
* refactor: refactored/updated tests
Update the contributors test (which wasn't already committed somehow) and tweaked the
`format-contribution-type` test.
* docs(readme): removed doctoc
BREAKING CHANGE: (in 2babe26b08) The resulting contributors table is in HTML/CSS instead of being in Markdown.
* refactor(generate): removed the style from the generation
Removed the `<style>` block from the generated HTML code as it's redundant on Github (since it's one
of the non-whitelisted tags). The `README.md` was also updated reflecting the breaking changes.
* refactor(generate): image height and tweaks
Added `height` to images for avatars, quoted some `<table>` attributes and updated `README.md`
* docs: drop TOC
* chore(package): added commitizen
I added `git-cz` (commitizen) with the angular adapter (which seems to work)
* docs(readme): added cz badge
Added the badge to indicate the commitizen-friendliness of this repo.
* revert: removed the category changes from another PR
It removes the addition of a maintenance category to keep them separated.
* feat(contribution-type): added maintenance type
fixes#111
* docs(categories): added maintenance category
* refactor: changed the maintenance symbol
* refactor: alphabetical listing fix
I moved the `maintenance` blocks/lines to the correct locations
* feat(format-contributor): added `alt` attributes
I added `alt` attributes to `img` tags which specifies the name of the
contributor in them (for accessibility purposes).
* docs: added @Berkmann18
I added myself (I forgot to do that) for code (cf. my previous commit),
test and doc.
<!--
Thanks for your interest in the project. Bugs filed and PRs submitted are appreciated!
Please make sure that you are familiar with and follow the Code of Conduct for
this project (found in the CODE_OF_CONDUCT.md file).
Also, please make sure you're familiar with and follow the instructions in the
contributing guidelines (found in the CONTRIBUTING.md file).
If you're new to contributing to open source projects, you might find this free
video course helpful: http://kcd.im/pull-request
Please fill out the information below to expedite the review and (hopefully)
merge of your pull request!
-->
<!-- What changes are being made? (What feature/bug is being fixed here?) -->
**What**:
Add Security contribution type, as mentioned in https://github.com/kentcdodds/all-contributors/issues/106 and implemented in https://github.com/kentcdodds/all-contributors/pull/107
Also added user-testing as introduced as part of https://github.com/kentcdodds/all-contributors/pull/97/files
<!-- Why are these changes necessary? -->
**Why**:
All contributors!
<!-- How were these changes implemented? -->
**How**:
Me
<!-- Have you done all of these things? -->
**Checklist**:
<!-- add "N/A" to the end of each line that's irrelevant to your changes -->
<!-- to check an item, place an "x" in the box like so: "- [x] Documentation" -->
- [x] Documentation
- [ ] Tests - N/A
- [x] Ready to be merged <!-- In your opinion, is this ready to be merged as soon as it's reviewed? -->
- [x] Added myself to contributors table <!-- this is optional, see the contributing guidelines for instructions -->
<!-- feel free to add additional comments -->
<!--
Thanks for your interest in the project. Bugs filed and PRs submitted are appreciated!
Please make sure that you are familiar with and follow the Code of Conduct for
this project (found in the CODE_OF_CONDUCT.md file).
Also, please make sure you're familiar with and follow the instructions in the
contributing guidelines (found in the CONTRIBUTING.md file).
If you're new to contributing to open source projects, you might find this free
video course helpful: http://kcd.im/pull-request
Please fill out the information below to expedite the review and (hopefully)
merge of your pull request!
-->
<!-- What changes are being made? (What feature/bug is being fixed here?) -->
**What**: remove unnecessary space
<!-- Why are these changes necessary? -->
**Why**: generate command will not generate files because of extra space
<!-- How were these changes implemented? -->
**How**: remove space
<!-- Have you done all of these things? -->
**Checklist**:
<!-- add "N/A" to the end of each line that's irrelevant to your changes -->
<!-- to check an item, place an "x" in the box like so: "- [x] Documentation" -->
- [x] Documentation
- [x] Tests
- [ ] Ready to be merged <!-- In your opinion, is this ready to be merged as soon as it's reviewed? -->
- [ ] Added myself to contributors table <!-- this is optional, see the contributing guidelines for instructions -->
<!-- feel free to add additional comments -->
<!--
Thanks for your interest in the project. Bugs filed and PRs submitted are appreciated!
Please make sure that you are familiar with and follow the Code of Conduct for
this project (found in the CODE_OF_CONDUCT.md file).
Also, please make sure you're familiar with and follow the instructions in the
contributing guidelines (found in the CONTRIBUTING.md file).
If you're new to contributing to open source projects, you might find this free
video course helpful: http://kcd.im/pull-request
Please fill out the information below to expedite the review and (hopefully)
merge of your pull request!
-->
<!-- What changes are being made? (What feature/bug is being fixed here?) -->
**What**: Add a couple of sentences about running the from the command line with `npx` - they're almost verbetim the "heads up" that @kentcdodds suggested in https://github.com/jfmengels/all-contributors-cli/issues/92#issuecomment-391766876..
<!-- Why are these changes necessary? -->
**Why**: I was having difficulty understanding how to run the commands and I found this text in issue #92 super helpful - I figured it would be for others too 😄
<!-- How were these changes implemented? -->
**How**: Updated text in README
<!-- Have you done all of these things? -->
**Checklist**:
<!-- add "N/A" to the end of each line that's irrelevant to your changes -->
<!-- to check an item, place an "x" in the box like so: "- [x] Documentation" -->
- [x] Documentation
- [ ] Tests -- NA
- [x] Ready to be merged <!-- In your opinion, is this ready to be merged as soon as it's reviewed? -->
- [ ] Added myself to contributors table -- ironically I'm not sure how to do this 🤣 <!-- this is optional, see the contributing guidelines for instructions -->
<!-- feel free to add additional comments -->
* initial issue fix
* tests added
* revert unneisary lint change to untouched file
* added myself
* no contribution types when adding a contributor error handled
* revert commit 1bdb51eadf
* reverted readme back to commit# f697c73c48
* further reverted Readme to master
* removed generated index from rm
* removed generated index from rm
* breaking change to cli fixed:
* Update prompt.js
* Update prompt.js
* added code and test in my contribution
* list of invalid contributions added in error message
Closes#71
* Change script name and add yarn
The script name suggested (`add`) will conflict with users of yarn.
So I modified the suggested name to `append` which is what it does. And now it can have a yarn example as well.
* remove yarn example
* namespace add
* feat: Add checking functionnality that compares contributors with GH data
* fix(check): Use the info from config file, paginate GH data
* doc(check): Document the new check command
* fix(eslint): Add missing semicolon
* tests: Add tests for utils.check
* fix: Check for code and test only
* refactor: use includes and correct awaits
* refactor: more includes and template literals
* Add alt text (description) on all emoji
Using markdown its possible to attach an alt text (really the title
attribute) on a link, where the value of the link is the the emoji. As
for the actual href, using #xxxxx lets you not mess with the navigation
assuming you have unique keys. In my example, I'm simply using the
emoji's key and github user name (i.e., `<emoji-username>`).
All emojis are links even if they don't have any real url attached.
For example, `[👀](#eyes-kevinjalbert "Reviewed Pull Requests")`
* Add kevinjalbert to all-contributorsrc
