Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Issue #41 - Migrate to use go-whatsup-client #45

Merged
merged 3 commits into from
Oct 3, 2023
Merged

Issue #41 - Migrate to use go-whatsup-client #45

merged 3 commits into from
Oct 3, 2023

Commits on Oct 3, 2023

  1. Issue #41 - Migrate to use go-whatsup-client 

    - Import `go-whatsup-client`.
- Convert statuspage.io and slack `ReadStatus()` to take in the whatsup client and use it to get a status page.
- Add service name and page URL as fields to the `statuspageio.ClientReader` struct. These are used when making the call via the whatsup client.
- Pass a client into `GetOverview()` and create the appropriate struct based on the service type of the site. The client then gets passed into the `ReadStatus()` method associated with the struct type.
- Clean out all the now dead code.
- Polish up documentation.
- Comment out goimports pre-commit hook for now. Seems like there isn't a Go 1.21 compatible version yet...
    @sprak3000
    sprak3000 committed Oct 3, 2023
    Configuration menu
    Copy the full SHA
    708f43b View commit details
    Browse the repository at this point in the history

  2. Issue #41 - Migrate to use go-whatsup-client 

    - Update go version in CI.
    @sprak3000
    sprak3000 committed Oct 3, 2023
    Configuration menu
    Copy the full SHA
    4602b23 View commit details
    Browse the repository at this point in the history

  3. Issue #41 - Migrate to use go-whatsup-client 

    - Fix revive install.
    @sprak3000
    sprak3000 committed Oct 3, 2023
    Configuration menu
    Copy the full SHA
    1eeac12 View commit details
    Browse the repository at this point in the history