Add tickstem/uptime to DevOps section

[mike392]

Required links

• Forge link (github.com, gitlab.com, etc): https://github.com/tickstem/uptime
• pkg.go.dev: https://pkg.go.dev/github.com/tickstem/uptime
• goreportcard.com: https://goreportcard.com/report/github.com/tickstem/uptime
• Coverage service link: https://app.codecov.io/gh/tickstem/uptime

Pre-submission checklist

• I have read the Contribution Guidelines
• I have read the Quality Standards

Repository requirements

• The repo has a go.mod file and at least one SemVer release (vX.Y.Z).
• The repo has an open source license.
• The repo documentation has a pkg.go.dev link.
• The repo documentation has a goreportcard link (grade A- or better).
• The repo documentation has a coverage service link.
• The repo has a continuous integration process (GitHub Actions, etc.).
• CI runs tests that must pass before merging.

Pull Request content

• This PR adds/removes/changes only one package.
• The package has been added in alphabetical order.
• The link text is the exact project name.
• The description is clear, concise, non-promotional, and ends with a period.
• The link in README.md matches the forge link above.

Category quality

• The packages around my addition still meet the Quality Standards.

[github-actions]

Automated Quality Checks

Required checks

✅ Repo: accessible, has go.mod and SemVer release
✅ pkg.go.dev: OK
✅ Go Report Card: OK (grade unknown)

Additional checks

⚠️ License: no open source license detected

How to fix: Add a LICENSE file to your repository root.
Choose one at https://choosealicense.com — common choices for Go projects: MIT, Apache-2.0, BSD-3-Clause.
⚠️ Maturity: repo appears to have less than 5 months of history
How to fix: Your repository needs at least 5 months of history since the first commit.
Please resubmit after the repository meets this requirement.
✅ CI/CD: GitHub Actions workflows detected
✅ README: present
✅ Coverage: link accessible

These checks are automated and do not replace maintainer review. See CONTRIBUTING.md for full guidelines.

---

PR Diff Validation

Content checks

✅ Files changed: only README.md
✅ Single item: one package added
✅ Link consistency: README link matches forge link in PR body
✅ Description: ends with punctuation
✅ Description tone: no promotional language detected
✅ Category size: DevOps Tools has 104 items

Warnings

⚠️ Link text: tickstem/uptime differs from repo name uptime

How to fix: The link text should be the exact project name.
If the project name really is tickstem/uptime, this is fine. Otherwise change it to: - [uptime](https://github.com/tickstem/uptime) - ...

Automated diff validation — does not replace maintainer review.