Similar to CloneRepo the handler tries to send two messages one after
the other. Leave it to WebhookRegistered handler to kick off the
ValidateRepo. Also update the README with the correct message sequence.
The Github routine for registering a new webhook, wasn't removing any
existing matching webhooks. There is a test for this, but it doesn't
assert that the delete requests are made. (This is a limitation of
kxio).
Closeskemitix/git-next#102
### Bug Fixes
- Github: use correct url to check CI status
([46e2871](46e2871e17))
- Github: as soon as any check fails, ignore any pending
([7b280a2](7b280a2a0a))
### Documentation
- Update installation instructions
([044790a](044790a019))
- Flesh out and update README
([8d42945](8d42945c37))
- Fix typos and clarifications
([9462957](9462957c5e))
### Miscellaneous Tasks
- Remove unused dependencies
([235aee8](235aee8b11))
- Add grcov-coverage as an alternate report generation recipe
([d67b821](d67b821130))
- Ignore coverage metadata (profraw files)
([8609652](8609652928))
### Refactor
- Config: use thiserror and move tests about
([0b8e41a](0b8e41a8ec))
- Git: use thiserror and cleanup errors
([621e599](621e599b31))
- Server: use thiserror
([e29c274](e29c274aaf))
### Testing
- Add more tests to config crate
([1010eae](1010eaec64))
- Add more tests to forge crate
([98839c8](98839c8a00))
- Add more tests to forge-forgejo crate
([c189aa3](c189aa3ad3))
- Add more tests to forge-github crate
([309e523](309e523cfe))
