e133b43599
wip: ci: factor out deployment into separate steps for better org.
/ pipeline-info (pull_request) Successful in 1s
/ build (pull_request) Successful in 41s
/ deploy-prod (pull_request) Failing after 39s
/ deploy-staging (pull_request) Successful in 11s
2025-07-26 16:27:37 +02:00
cb089a6d05
ci: make step conditions more structured
...
/ pipeline-info (pull_request) Successful in 1s
/ build (pull_request) Successful in 41s
Either have a step always be executed, be executed for prod or be
executed for a PR (staging) and use the same conditions for each of
these cases.
2025-07-26 16:11:02 +02:00
f9f3a82f23
ci: factor out "Pipeline info" step into separate job for nicer org.
/ pipeline-info (pull_request) Successful in 1s
/ build (pull_request) Successful in 48s
2025-07-26 16:00:10 +02:00
3ea764708a
Theme,CI: Update hugo and fix for hugo v0.146
...
/ build (push) Successful in 20s
hugo 0.146.0 refactored the template system and changed where some internal templates are located.
2025-07-26 09:44:59 +02:00
102b3cb4db
Theme: Fix summary for v0.134.0
...
Hugo v0.134.0 changed the return value of the content summary to always be HTML instead of plain text.
So we don't need the work around any more.
2025-07-26 09:44:59 +02:00
f173698126
Theme: Fix author names for hugo v0.123.0/ v0.123.3
...
Hugo v0.123.0 started to capitalize the title of term pages. v0.123.3 introduced config parameters to disable that behaviour.
2025-07-26 09:44:59 +02:00
601b0054e2
CI: Move from gitlab to hugomods docker image
...
See https://gitlab.com/pages/hugo#deprecation-of-container-registry
2025-07-26 09:44:59 +02:00
364ec75a45
Update Node.js to v22
/ build (pull_request) Successful in 43s
/ cleanup-staging (pull_request) Successful in 3s
/ build (push) Successful in 16s
2025-07-23 22:31:18 +02:00
0b0eb7a934
[REFACTOR] Fix markdown formatting and trailing whitespace
/ build (push) Successful in 16s
2025-07-23 20:16:56 +02:00
714014bc25
Update Tür/Telefon ( #86 )
...
/ build (push) Successful in 16s
Reviewed-on: #86
Reviewed-by: lilly <lilly@noreply.git.hamburg.ccc.de>
Reviewed-by: jtbx <jtbx@noreply.git.hamburg.ccc.de>
Co-authored-by: Stefan Bethke <stb@lassitu.de>
Co-committed-by: Stefan Bethke <stb@lassitu.de>
2025-07-23 14:05:44 +02:00
d81e83ffdb
Kommentar von Kantorkel zur Messerattacke am Hbf ( #84 )
...
/ build (push) Successful in 15s
Co-authored-by: n0th1ng <n0th1ngm4tt3r5@protonmail.com>
Reviewed-on: #84
2025-05-30 15:38:39 +02:00
71b7554bd2
Added Netzpolitischer Easterhegg Blogpost ( #82 )
...
/ build (push) Successful in 15s
Reviewed-on: #82
Reviewed-by: lilly <lilly@noreply.git.hamburg.ccc.de>
Co-authored-by: n0th1ng <n0th1ngm4tt3r5@protonmail.com>
Co-committed-by: n0th1ng <n0th1ngm4tt3r5@protonmail.com>
2025-04-09 17:51:48 +02:00
0112d3bf3e
Added Event ( #81 )
...
/ build (push) Successful in 14s
Bitte mergen sobald möglich
Reviewed-on: #81
Reviewed-by: lilly <lilly@noreply.git.hamburg.ccc.de>
Co-authored-by: n0th1ng <n0th1ngm4tt3r5@protonmail.com>
Co-committed-by: n0th1ng <n0th1ngm4tt3r5@protonmail.com>
2025-03-20 12:04:39 +01:00
225d642318
Add link to events page ( #80 )
...
/ build (push) Successful in 14s
Reviewed-on: #80
Co-authored-by: Stefan Bethke <stb@lassitu.de>
Co-committed-by: Stefan Bethke <stb@lassitu.de>
2025-03-10 15:15:00 +01:00
d4b6a9b1e5
Create first draft for TdoH page. ( #79 )
...
/ build (push) Successful in 13s
Reviewed-on: #79
Co-authored-by: dl8xas <sons@indusi.net>
Co-committed-by: dl8xas <sons@indusi.net>
2025-03-10 15:03:51 +01:00
e8ab1ddc81
make staging CI show blog posts with future publish date
...
/ build (pull_request) Successful in 38s
/ cleanup-staging (pull_request) Successful in 2s
/ build (push) Successful in 14s
Co-authored-by: Dario <dario@bauschutt.org>
Suggested-by: Dario <dario@bauschutt.org>
2025-02-08 22:56:09 +01:00
bb32b6d858
content/blog/2024/Brettpspielabend hinzugefügt ( #76 )
...
/ build (push) Successful in 14s
Co-authored-by: dario <446-dario@users.noreply.gitlab.hamburg.ccc.de>
Reviewed-on: #76
Co-authored-by: fraeuleinwusel <fraeuleinwusel@noreply.git.hamburg.ccc.de>
Co-committed-by: fraeuleinwusel <fraeuleinwusel@noreply.git.hamburg.ccc.de>
2025-02-08 20:17:02 +01:00
5531aa2b0b
content/imprint/index.md steuerlicher hinweis hinzugefügt ( #75 )
...
/ build (push) Successful in 15s
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>
2025-01-15 19:27:40 +01:00
skye gänseblum
9571f804ba
Verständlichkeit
/ build (pull_request) Successful in 38s
/ cleanup-staging (pull_request) Successful in 2s
/ build (push) Successful in 14s
2024-11-29 20:10:58 +01:00
skye gänseblum
061a496341
Tippfehler Titel
/ build (pull_request) Successful in 37s
2024-11-29 19:48:53 +01:00
skye gänseblum
f8f65f5a57
Ankündigung Dezember-FreiTalk
/ build (pull_request) Successful in 38s
2024-11-29 18:56:21 +01:00
99572011bc
Clarify dates ( #73 )
...
/ build (push) Successful in 14s
Reviewed-on: #73
Co-authored-by: Stefan Bethke <stb@lassitu.de>
Co-committed-by: Stefan Bethke <stb@lassitu.de>
2024-11-17 11:29:35 +01:00
fcf4a46a1d
Vouchers are done ( #72 )
...
/ build (push) Successful in 13s
Reviewed-on: #72
Co-authored-by: Stefan Bethke <stb@lassitu.de>
Co-committed-by: Stefan Bethke <stb@lassitu.de>
2024-11-05 16:41:05 +01:00
b3de8ec33d
Ticket-Click-Party ( #70 )
...
/ build (push) Successful in 13s
Reviewed-on: #70
2024-11-02 10:42:25 +01:00
9c8c3ae28c
typo ( #71 )
...
/ build (push) Successful in 13s
Reviewed-on: #71
Co-authored-by: Stefan Bethke <stb@lassitu.de>
Co-committed-by: Stefan Bethke <stb@lassitu.de>
2024-11-02 10:18:21 +01:00
2f54794d99
Add screenshot for target email ( #69 )
...
/ build (push) Successful in 14s
Reviewed-on: #69
Co-authored-by: Stefan Bethke <stb@lassitu.de>
Co-committed-by: Stefan Bethke <stb@lassitu.de>
2024-10-23 08:23:16 +02:00
eadbdfd0d7
clarify 38c3 voucher payment process
/ build (push) Successful in 14s
2024-10-22 00:54:48 +02:00
c8bd6e176b
Typo ( #68 )
...
/ build (push) Successful in 15s
Reviewed-on: #68
Co-authored-by: Stefan Bethke <stb@lassitu.de>
Co-committed-by: Stefan Bethke <stb@lassitu.de>
2024-10-21 19:52:44 +02:00
f2573eff5e
Add info page for vouchers for 38c3 ( #66 )
...
/ build (push) Successful in 14s
Reviewed-on: #66
Co-authored-by: Stefan Bethke <stb@lassitu.de>
Co-committed-by: Stefan Bethke <stb@lassitu.de>
2024-10-21 19:48:38 +02:00
70a34c517d
Korrekte Nummer für den Club verwenden
/ build (pull_request) Successful in 36s
/ cleanup-staging (pull_request) Successful in 2s
/ build (push) Successful in 13s
2024-08-06 19:11:55 +02:00
568f36a0b3
Configure Renovate ( #61 )
...
/ build (push) Successful in 13s
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>
2024-07-29 09:48:38 +02:00
36a34782ce
openchaos begins later on 2024-07-12
/ build (pull_request) Successful in 36s
/ cleanup-staging (pull_request) Successful in 2s
/ build (push) Successful in 13s
2024-07-10 18:43:21 +02:00
4222ac7b2b
[blog] openchaos am 14. juni fällt aus
...
/ build (push) Successful in 12s
Co-authored-by: dario <446-dario@users.noreply.gitlab.hamburg.ccc.de>
Co-committed-by: dario <446-dario@users.noreply.gitlab.hamburg.ccc.de>
2024-06-08 20:18:23 +02:00
63d3f4459d
Theme: Fix robots partial "isset on nil" warning
...
/ build (pull_request) Successful in 40s
/ cleanup-staging (pull_request) Successful in 1s
/ build (push) Successful in 12s
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.
2024-04-20 18:14:41 +02:00
e0c46fb4e2
Added new ctf event
/ build (push) Successful in 13s
2024-04-17 20:58:29 +02:00
462fb7ed68
[FIX] failed build on some newer hugo versions
...
/ build (pull_request) Successful in 40s
/ cleanup-staging (pull_request) Successful in 2s
/ build (push) Successful in 13s
might need v0.123.0 or greater
2024-03-12 21:22:28 +01:00
76dcc69074
CSS: Less bottom margin for headings
/ build (push) Successful in 13s
2024-03-07 20:15:01 +01:00
7e29bd5369
Theme: Keep current event for 6 hours after start date
...
/ build (pull_request) Successful in 39s
/ cleanup-staging (pull_request) Successful in 2s
/ build (push) Has been cancelled
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.
2024-03-07 20:11:29 +01:00
765d271531
Home: Add "read more" link to announcement summary
...
/ build (pull_request) Successful in 40s
/ cleanup-staging (pull_request) Successful in 2s
/ build (push) Successful in 13s
Adding an ellipsis doesn't really work for both cases.
2024-03-02 22:09:27 +01:00
0f533e21e5
Theme: Add link to "Z9" location
/ build (push) Successful in 13s
2024-02-20 21:27:28 +01:00
skye gänseblum
9b577a908f
Tag des offenen Hackspace Ankündigung
/ build (push) Successful in 12s
2024-02-20 21:26:01 +01:00
e1a8a4d90e
fetch-calendar: set start time to 6 h in the past
...
/ build (push) Successful in 12s
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.
2024-02-13 19:17:01 +01:00
7d492980b8
Theme: use right locale in calendar-table
/ build (push) Successful in 13s
2024-02-11 20:10:22 +01:00
8607882719
Theme: Add favicon
/ build (pull_request) Successful in 39s
/ cleanup-staging (pull_request) Successful in 1s
/ build (push) Successful in 12s
2024-02-08 22:14:26 +01:00
74f32d0138
Add lactf blog entry
/ build (pull_request) Successful in 39s
/ cleanup-staging (pull_request) Successful in 1s
/ build (push) Successful in 13s
2024-02-07 22:38:00 +01:00
8a66b0a361
fix doorstatus not updating every minute
...
/ build (pull_request) Successful in 40s
/ cleanup-staging (pull_request) Successful in 2s
/ build (push) Successful in 13s
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
2024-02-02 15:44:59 +01:00
61f22607d6
fix typo
/ build (pull_request) Successful in 40s
/ cleanup-staging (pull_request) Successful in 2s
/ build (push) Successful in 13s
2024-02-02 15:04:05 +01:00
dec278910e
CI: Fix lastmod property of articles
...
/ build (pull_request) Successful in 39s
/ cleanup-staging (pull_request) Successful in 2s
/ build (push) Successful in 13s
We use the git commit to determine the lastmod date, but the checkout action uses a shallow clone by default.
2024-02-01 20:23:23 +01:00
8c2684abef
CI: Fix deploy on schedule
/ build (push) Successful in 12s
2024-02-01 20:11:25 +01:00
d5fc2adfe1
CI: Post staging URL to PR once (on open event)
/ build (pull_request) Successful in 38s
/ cleanup-staging (pull_request) Successful in 1s
/ build (push) Successful in 13s
2024-01-28 13:04:48 +01:00