self-hosted/uptime-kuma - uptime-kuma - Gitea: Git with a cup of tea

self-hosted/uptime-kuma

mirror of https://github.com/louislam/uptime-kuma.git synced 2024-12-22 22:13:20 +02:00

Author	SHA1	Message	Date
Cassandra	b287a25de7	feat: structured logging (JSON) (#5118 ) Some checks failed Merge Conflict Labeler / Labeling (push) Has been skipped Details json-yaml-validate / json-yaml-validate (push) Successful in 12s Details Auto Test / check-linters (push) Failing after 22m10s Details Auto Test / auto-test (18, ARM64) (push) Has been cancelled Details Auto Test / auto-test (18, macos-latest) (push) Has been cancelled Details Auto Test / auto-test (18, ubuntu-latest) (push) Has been cancelled Details Auto Test / auto-test (18, windows-latest) (push) Has been cancelled Details Auto Test / auto-test (20.5, ARM64) (push) Has been cancelled Details Auto Test / auto-test (20.5, macos-latest) (push) Has been cancelled Details Auto Test / auto-test (20.5, ubuntu-latest) (push) Has been cancelled Details Auto Test / auto-test (20.5, windows-latest) (push) Has been cancelled Details Auto Test / armv7-simple-test (18, ARMv7) (push) Has been cancelled Details Auto Test / armv7-simple-test (20, ARMv7) (push) Has been cancelled Details Auto Test / e2e-test (push) Has been cancelled Details Automatically close stale issues / stale (push) Successful in 16s Details CodeQL / Analyze (go) (push) Failing after 56s Details CodeQL / Analyze (javascript-typescript) (push) Failing after 27s Details	2024-09-24 17:51:21 +08:00
Elliot Matson	5bc68fe0a7	Google chat cards (#3928 ) Co-authored-by: Frank Elsinga <frank@elsinga.de>	2024-03-20 12:58:28 +01:00
Frank Elsinga	a9a1cf1353	Chore: General notification reformatting (#3182 ) - I unified where in file the name of `NotificationProvider.name` is placed - I made sure that all the providers adhere to the signature of `NotificationProvider.send()` - I made sure that all the providers use `okMsg` if returning success messages directly from the function. Here a discussion should be had: Should this be refactored into a constant of `NotificationProvider`? I could imagine that `NotificationProvider.SENDING_SUCCESSFULL` could be a suitable alternative. - I made sure all providers have the URL they `POST`/`GET` to be extraced into a variable. => refactored this way due to Nelsons suggestion	2024-03-14 14:21:15 +01:00
Matthew Nickson	8a92054c2b	Added JSDoc to ESLint (#3529 ) * Added JSDoc to eslint rules Signed-off-by: Matthew Nickson <mnickson@sidingsmedia.com> * Fixed JSDoc eslint errors Signed-off-by: Matthew Nickson <mnickson@sidingsmedia.com> * Update the check-linters workflow to Node.js 20 --------- Signed-off-by: Matthew Nickson <mnickson@sidingsmedia.com> Co-authored-by: Louis Lam <louislam@users.noreply.github.com>	2023-08-11 15:46:41 +08:00
Louis Lam	649f3106e1	Enforce semicolon, fix format globally	2022-04-14 01:20:54 +08:00
Thomas LÉVEIL	46fa6a56fa	fix `TypeError: Cannot read property 'id' of null` when testing a Google Chat notification see https://github.com/louislam/uptime-kuma/issues/1126#issuecomment-1006343423	2022-01-06 08:48:12 +01:00
Philipp Bischoff	bcc3cec7d6	extract translation for notification type	2022-01-05 23:57:40 +01:00
Philipp Bischoff	f8c5015e3f	fix google chat type mismatch	2022-01-05 23:44:14 +01:00
Philipp Bischoff	a6072a0e30	google chat: only show offline message in notification when service went down	2021-12-15 13:40:21 +01:00
Philipp Bischoff	a71569379e	add missing import	2021-12-12 00:01:12 +01:00
Philipp Bischoff	8050cb8e99	implement google chat notification type	2021-12-11 23:43:12 +01:00