mirror of
https://github.com/louislam/uptime-kuma.git
synced 2025-06-29 15:14:26 +02:00
5336b05a7f
Some checks are pending
Auto Test / auto-test (18, ARM64) (push) Blocked by required conditions
Auto Test / auto-test (18, macos-latest) (push) Blocked by required conditions
Auto Test / auto-test (18, ubuntu-latest) (push) Blocked by required conditions
Auto Test / auto-test (18, windows-latest) (push) Blocked by required conditions
Auto Test / auto-test (20, ARM64) (push) Blocked by required conditions
Auto Test / auto-test (20, macos-latest) (push) Blocked by required conditions
Auto Test / auto-test (20, ubuntu-latest) (push) Blocked by required conditions
Auto Test / auto-test (20, windows-latest) (push) Blocked by required conditions
Auto Test / armv7-simple-test (18, ARMv7) (push) Waiting to run
Auto Test / armv7-simple-test (20, ARMv7) (push) Waiting to run
Auto Test / check-linters (push) Waiting to run
Auto Test / e2e-test (push) Waiting to run
CodeQL / Analyze (push) Waiting to run
Merge Conflict Labeler / Labeling (push) Waiting to run
validate / json-yaml-validate (push) Waiting to run
validate / validate (push) Waiting to run
3.6 KiB
3.6 KiB
❗ Important Announcements
Click here for more details:
⚠️ Please Note: We do not accept all types of pull requests, and we want to ensure we don’t waste your time. Before submitting, make sure you have read our pull request guidelines: Pull Request Rules
🚫 Please Avoid Unnecessary Pinging of Maintainers
We kindly ask you to refrain from pinging maintainers unless absolutely necessary. Pings are for critical/urgent pull requests that require immediate attention.
📋 Overview
- What problem does this pull request address?
- Please provide a detailed explanation here.
- What features or functionality does this pull request introduce or enhance?
- Please provide a detailed explanation here.
- Relates to #issue-number
- Resolves #issue-number
🛠️ Type of change
- 🐛 Bugfix (a non-breaking change that resolves an issue)
- ✨ New feature (a non-breaking change that adds new functionality)
- ⚠️ Breaking change (a fix or feature that alters existing functionality in a way that could cause issues)
- 🎨 User Interface (UI) updates
- 📄 New Documentation (addition of new documentation)
- 📄 Documentation Update (modification of existing documentation)
- 📄 Documentation Update Required (the change requires updates to related documentation)
- 🔧 Other (please specify):
- Provide additional details here.
📄 Checklist
- 🔍 My code adheres to the style guidelines of this project.
- 🦿 I have indicated where (if any) I used an LLM for the contributions
- ✅ I ran ESLint and other code linters for modified files.
- 🛠️ I have reviewed and tested my code.
- 📝 I have commented my code, especially in hard-to-understand areas (e.g., using JSDoc for methods).
- ⚠️ My changes generate no new warnings.
- 🤖 My code needed automated testing. I have added them (this is an optional task).
- 📄 Documentation updates are included (if applicable).
- 🔒 I have considered potential security impacts and mitigated risks.
- 🧰 Dependency updates are listed and explained.
- 📚 I have read and understood the Pull Request guidelines.
📷 Screenshots or Visual Changes
- UI Modifications: Highlight any changes made to the user interface.
- Before & After: Include screenshots or comparisons (if applicable).
| Event | Before | After |
|---|---|---|
UP |
 |
|
DOWN |
|
|
| Certificate-expiry | |
|
| Testing | |
|