@kibibit/achievibit

achievibit

---

• Achievements system as a GitHub WebHook.
• Get achievements on different characteristics of your pull requests
• Use the achievibit chrome extension to see achievibit inside GitHub

how to use

we're working on implementing GitHub oAuth to support some extra features.

stay tuned

achievibit needs to be integrated into each enabled repository via a webhook.

1. Go to your main repository page
2. click on Settings
3. on the sidebar, click on Webhooks
4. click on add webhook
5. paste achievibit's url (http://achievibit.kibibit.io) into the payload url
6. change Content type to application/json
7. on Which events would you like to trigger this webhook?, select Let me select individual events. and check Pull request and Pull request reviews

Maybe sometime later we'll also support repo achievements. open an issue if you're interested :-)

Chrome extension

You can install our chrome extension to see achievements in github profiles, and see an animation everytime you get an achievement

Add our shield to your project's README

We've just started, and we want to spread the word. We would really appreciate if you'll add our shield if you think achievibit is worth talking about

copy this snippet to any markdown file

• shield: number of achievable achievements

[![Supported achievements](http://achievibit.kibibit.io/achievementsShield)](https://achievibit.kibibit.io)

Contributors

Want to file a bug, contribute some code, or improve documentation? Excellent! Read up on our guidelines for contributing.

You can check out some easy to start with issues in the Easy Pick.

Contributor Code of Conduct

Please note that this project is released with a Contributor Code of Conduct.

By participating in this project you agree to abide by its terms.

License

MIT License

Copyright (c) 2017 Neil Kalman <[e-mail]>

Changelog

2.0.0-beta.1 (2021-04-18)

Bug Fixes

• app: small nits: fix plural and hide warning (d3cdfdc)

Features

• api: add user and repo controllers (298c4bf)
• models: add user and repo models (5278b84)
• app: small nits across the app (7992c4b)
• release: start releasing a beta version (1abfec7)
• github-actions: try caching ~/.npm (f5d99c5)

ref

• init: make room for 2nd version (35c7b2c)

BREAKING CHANGES

• init: From this point on, the application is going to work differently, so this is definitely a breaking change that should start the 2nd version. Even after feature parity, the structure will be different in this new version (api route moves, client side will be fancier, etc.).