Passage von https://www.ccc.de/de/support übernommen und in Absprache mit dario hier eingefügt.
Signed-off-by: dickmaulrussler <dickmaulrussler@noreply.git.hamburg.ccc.de>
Co-authored-by: dario <446-dario@users.noreply.gitlab.hamburg.ccc.de>
Reviewed-on: #75
Reviewed-by: christian <c6ristian+git-ccchh@christian.moe>
Co-authored-by: dickmaulrussler <dickmaulrussler@noreply.git.hamburg.ccc.de>
Co-committed-by: dickmaulrussler <dickmaulrussler@noreply.git.hamburg.ccc.de>
Welcome to [Renovate](https://github.com/renovatebot/renovate)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.
🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.
---
### Detected Package Files
* `.forgejo/workflows/cleanup.yaml` (github-actions)
* `.forgejo/workflows/deploy.yaml` (github-actions)
* `.gitlab-ci.yml` (gitlabci)
### Configuration Summary
Based on the default config's presets, Renovate will:
- Start dependency updates only once this onboarding PR is merged
- Enable Renovate Dependency Dashboard creation.
- Use semantic commit type `fix` for dependencies and `chore` for all others if semantic commits are in use.
- Ignore `node_modules`, `bower_components`, `vendor` and various test/tests directories.
- Group known monorepo packages together.
- Use curated list of recommended non-monorepo package groupings.
- Apply crowd-sourced package replacement rules.
- Apply crowd-sourced workarounds for known problems with packages.
🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to `renovate.json` in this branch. Renovate will update the Pull Request description the next time it runs.
---
### What to Expect
It looks like your repository dependencies are already up-to-date and no Pull Requests will be necessary right away.
---
❓ Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section.
If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions).
---
This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-config-hash:e80b4e42a3043bc12fa0640db4bac392d2bf770acf841360d7c8ceeeac2ec1a9-->
Reviewed-on: #61
Co-authored-by: Renovate <no-reply@git.hamburg.ccc.de>
Co-committed-by: Renovate <no-reply@git.hamburg.ccc.de>
As not all pages have the robots param defined, we got a warning:
WARN calling IsSet with unsupported type "invalid" (<nil>) will always return false.
This is solved by adding an additional "isset" check.
Events are shown in the "Neuigkeiten" section until their start date has been reached.
As we deploy quite often, this means, that the currently running event will disappear when it's still going.
As we don't know the end date, just show them for 6 more hours.
Only showing the current event if it started less than 6 hours in the past
should be fine. We rarely have longer events and those usually had an
announcement post anyways.
roomstate.js incorrectly used setTimeout() instead of setInterval() to
call the door status. This caused the status to only be updated once
after the initial page load, instead of once every minute
