Files
challenge_status_tracker/ctf_status.env.example
T
Casually9790andClaude Opus 5.5 e8a04fe415 Source challenge status from GitLab instead of Nextcloud
Read the README.md of every repo in the GitLab challenges group via the
REST API and rework the HedgeDoc note for project tracking: challenges
ready for infra testing first, then status by category and a
category x difficulty grid. Free-text status/difficulty/category values
are normalised; untouched templates and repos scheduled for deletion
are left out of the counts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 16:12:35 +02:00

16 lines
759 B
Bash

# cp to ctf_status.env and chmod 600 (a plain .env next to the script works too)
# --- GitLab: the group holding one repo per challenge -----------------------
GITLAB_GROUP_URL=https://gitlab.lrz.de/h4tum-ctf/h4tum-ctf-2026/challenges
# fine-grained personal access token, scoped to that group, with
# Project: Read (list the repos)
# Repository: Read (download each README.md)
GITLAB_TOKEN=glpat-xxxxxxxxxxxxxxxxxxxx
# --- HedgeDoc: the existing note that gets overwritten every run ------------
# full URL of the note (its permission must be "freely" so an anonymous
# run may write to it), e.g. https://hedgedoc.cit.tum.de/AbCdEf123
HEDGEDOC_NOTE=
# YAML front-matter tags written at the top of the note
HEDGEDOC_TAGS=Logistics, h4tum CTF 2026