Projektauswahl

Wähle deine Top 3 Favoriten für jede Zeitspanne

\n\n \n

\n\n \n \n\n","children",[],[301],"8ed05d6f-e1f4-4acd-a1fe-679c541bf1b8","parent-proposals-overview.html","019e8205-0429-72dd-a700-b3773cd0cfb0",24,["D",1780657371419],"\n\n\n \n \n Projektvorschläge nach Zeitslot\n \n\n\n

Projektwoche · Überblick

Projektvorschläge nach Zeitslot

\n Diese Ansicht gruppiert alle eingereichten Vorschläge nach Tag und verfügbarem Zeitslot. Ein Projekt erscheint in jedem Slot, den die Eltern im Formular markiert haben.\n

\n Zum Einreichungsformular\n Zum Adminbereich\n

\n\n

\n\n \n\n\n",[],[310],"f7d35ed4-5d88-11f1-b3b4-1607ee4eb77e","parent-proposal.html","019e8205-0429-72dd-a700-ac4b18e15abf",["D",1780297827276],"\n\n\n \n \n Weiterleitung...\n\n\n

Zur Eltern-Projektseite

\n\n\n",[],[318],"f7d2ae58-5d88-11f1-b3b4-1607ee4eb77e","parent-project-proposal.html","019e8205-0429-72dd-a700-aafc1f1bf485",["D",1780297827276],"\n\n\n \n \n Projekt anbieten - Projektwoche\n \n\n\n

Projektwoche · Elternformular

Ein Projekt für die Woche anbieten

\n Du hast eine Idee, die du gern mit einer Gruppe von Kindern umsetzen möchtest? Hier kannst du sie einreichen. Der Vorschlag landet zuerst beim Orga-Team und wird erst nach Prüfung in den Projektplan übernommen.\n

\n Ohne Registrierung\n Ein Formular, kein Passwort, keine extra Hürde.\n

\n Mit Orga-Prüfung\n Ihr markiert nur Verfügbarkeit, die Platzierung machen wir.\n

\n Auch für 2 Zeitslots\n Mehrteilige Projekte werden als zusammenhängender Block verstanden.\n

\n\n \n

\n\n

Elternteil

Kontakt für Rückfragen und Abstimmung mit dem Orga-Team.

\n\n

\n Name *\n \n

\n E-Mail\n \n

\n\n

\n Kind / Bezug zur Schule\n \n

\n\n

Projektidee

Der öffentliche Teil sollte für Kinder und Eltern verständlich formuliert sein.

\n\n

\n Projekttitel *\n \n

\n\n

\n Kurzbeschreibung *\n \n

\n\n

\n Mit-Anbietende / zweite Begleitperson\n \n

\n\n

\n Min. Teilnehmende\n \n

\n Max. Teilnehmende\n \n

\n Dauer *\n \n

\n\n

\n Hinweis zu 2 Zeitslots\n

\n Dieses Projekt wird als zusammenhängender Block verstanden. Dieselben Kinder nehmen an beiden Zeitslots teil. Später soll die Auswahl im Kinderformular das automatisch berücksichtigen.\n

\n\n

Altersgruppen

Mehrere Gruppen sind möglich, falls das Projekt altersübergreifend geeignet ist.

\n\n

\n \n \n \n Delfine\n Klasse 1-3\n \n \n

\n \n \n \n Drachen\n Klasse 4-6\n \n \n

\n \n \n \n 7/8\n Klasse 7-8\n \n \n

\n \n \n \n 9/10\n Klasse 9-10\n \n \n

\n\n

\n Hinweise zur Altersgruppe\n \n

\n\n

Rahmen & Material

Hier sammeln wir alles, was für die Planung von Raum und Vorbereitung wichtig ist.

\n\n

\n Ort\n

\n \n \n Drinnen\n Tische, Wasser, ruhiger Raum oder andere Innenraumbedingungen.\n \n

\n \n \n Draußen\n Schulhof, Naturgelände oder wetterfeste Kleidung notwendig.\n \n

\n \n \n Egal\n Das Projekt kann flexibel drinnen oder draußen stattfinden.\n \n

\n\n

\n Raum- oder Platzbedarf\n \n

\n Material, das du mitbringst\n \n

\n\n

\n Material, das Kinder mitbringen sollen\n \n

\n Weitere Hinweise\n \n

\n\n

Verfügbarkeit

Bitte alle Zeitslots markieren, an denen du das Projekt anbieten könntest. Die konkrete Einteilung übernehmen wir später.

\n\n

Dienstag

\n \n \n 09:00-10:30\n Slot 1 · 90 Minuten\n \n

\n \n \n 10:45-12:15\n Slot 2 · 90 Minuten\n \n

\n \n \n 12:45-13:30\n Slot 3 · 45 Minuten\n \n

\n\n

Mittwoch

\n \n \n 09:00-10:30\n Slot 4 · 90 Minuten\n \n

\n \n \n 10:45-12:15\n Slot 5 · 90 Minuten\n \n

\n \n \n 12:45-13:30\n Slot 6 · 45 Minuten\n \n

\n\n

\n Vorschläge werden jetzt separat gespeichert. Sie sind noch nicht an das restliche Projektwochen-System angebunden.\n

\n \n \n \n

\n\n \n\n

Danke, dein Vorschlag ist eingegangen.

\n Der Vorschlag wurde gespeichert. Unten siehst du alle bisher eingereichten Projekte.\n

\n\n \n

\n\n

Bisher eingereichte Vorschläge

Diese Liste ist vorerst nur für das Testen gedacht. Einträge lassen sich hier direkt wieder löschen.

Einträge werden geladen ...

\n\n \n\n\n",[],[325],"f7d2ac8c-5d88-11f1-b3b4-1607ee4eb77e","main.ts","019e8205-0429-72dd-a700-a6a6f6b77006",["D",1780297827276],"script","",[],[332],"9f5305d0-5d8c-11f1-b0c3-1607ee4eb77e","deno.json","9f53067a-5d8c-11f1-b0c3-1607ee4eb77e",4,["D",1780299397428],"{\n \"$schema\": \"https://raw.githubusercontent.com/denoland/deno/98f62cee78e85bfc47c62ed703777c6bc8794f1c/cli/schemas/config-file.v1.json\",\n \"lock\": false,\n \"compilerOptions\": {\n \"noImplicitAny\": false,\n \"strict\": true,\n \"types\": [\"https://www.val.town/types/valtown.d.ts\"],\n \"lib\": [\n \"dom\",\n \"dom.iterable\",\n \"dom.asynciterable\",\n \"deno.ns\",\n \"deno.unstable\"\n ]\n },\n \"lint\": {\n \"include\": [\"deno:/https/esm.town/**/*\"],\n \"rules\": {\n \"exclude\": [\"no-explicit-any\"]\n }\n },\n \"node_modules_dir\": false,\n \"experimental\": {\n \"unstable-node-globals\": true,\n \"unstable-temporal\": true,\n \"unstable-worker-options\": true,\n \"unstable-sloppy-imports\": true\n }\n}",[],[340],"f7d247ba-5d88-11f1-b3b4-1607ee4eb77e","assignment.html","019e8205-0429-72dd-a700-a03f648c8ad2",["D",1780297827276],"\n\n\n \n \n Kid-to-Project Assignment Optimizer\n \n \n \n \n\n\n

\n\n \n\n",[],[348],"66d69e51-63c5-4481-82f2-893573afc347","admin.html","019e8205-0429-72dd-a700-9d8f6bd4d3de",31,["D",1780658516457],9,"\n\n\n Administration - Projektauswahl\n \n\n\n

Admin-Bereich - Projektauswahl

\n\n

Antworten der Kinder

Alle abgegebenen Antworten auf einer eigenen Seite ansehen, filtern, sortieren und löschen.

\n Antworten ansehen →\n

\n\n

Projektzuteilung

Kinder nach ihren Erstwahlen gruppiert ansehen und Projekten zuteilen.

\n Zuteilung bearbeiten →\n

\n\n

Zuteilungen ansehen

Gespeicherte Zuteilungen in verschiedenen Ansichten prüfen und drucken.

\n Nach Kind →\n Nach Projekt →\n

\n\n

Projektvorschläge von Eltern

Das Formular für Eltern und die Übersicht nach Tag und Zeitslot öffnen.

\n Elternformular öffnen →\n Vorschläge ansehen →\n \n

\n\n

Zeitslots

Lade...

Neuen Zeitslot anlegen

\n \n \n \n \n

\n\n

Projekte

Lade...

Neues Projekt anlegen

\n \n \n \n \n \n \n \n

\n\n \n \n\n \n\n\n",[],[355],"bf66293d-64ae-4e18-ac8f-522de24e4d5f","admin-responses.html","019e8205-0429-72dd-a700-9b1b3658d34d",33,["D",1780658918670],2,"\n\n\n Antworten der Kinder - Projektauswahl\n \n\n\n \n\n

Abgaben gesamt

Kinder

\n\n \n\n \n\n

Lade...

\n\n \n\n\n",[],[364],"2f6a8acd-cd43-4662-b16c-df94cfcf0483","admin-assignments.html","019e8205-0429-72dd-a700-96a229cdbf1d",34,["D",1780658918706],"\n\n\n Projektzuteilung - Projektauswahl\n \n\n\n \n\n

Zuteilung berechnen

\n\n Zeitslot auswählen:\n \n\n \n \n\n \n\n

\n \n \n \n

\n\n

\n 💡 Hinweis: Nach der Berechnung kannst du Kinder per Drag-and-drop zwischen Projekten verschieben.\n

\n\n

Zuteilungsstatistik

Gesamtpunktzahl

1. Wahl

2. Wahl

3. Wahl

Nicht gewünscht

\n\n

Wähle einen Zeitslot aus und klicke auf \"Zuteilung berechnen\", um Ergebnisse zu sehen

\n\n \n

\n\n \n\n\n",[],[373],"b92dbabc-8b74-4471-84d3-be7478d2dbbb","admin-assignments-individual.html","019e8205-0429-72dd-a700-939230ea3375",["D",1780658918743],"\n\n\n Zuteilungen nach Kind - Projektauswahl\n \n\n\n \n\n

\n \n \n \n Erweiterte Ansicht mit Projektbeschreibungen anzeigen\n \n

\n\n

\n Lade Zuteilungen...\n

\n\n

\n Keine Zuteilungen gefunden\n

\n\n

\n \n

\n\n \n\n\n",[],[381],"378c5f1b-610e-4972-8335-0add1ede303a","admin-assignments-by-project.html","019e8205-0429-72dd-a700-8f6dbbdf0a2a",32,["D",1780658918630],"\n\n\n Zuteilungen nach Projekt - Projektauswahl\n \n\n\n \n\n

Zuteilungen nach Projekt - alle Zeitslots

\n\n \n\n

\n\n

Lade Zuteilungen...

\n\n \n\n\n",[],[388],"8fb1913a-cb01-474e-8172-4c085aad79d9","TODO.md","18573ec6-60ce-11f1-9d4e-1607ee4eb77e",29,["D",1780658357095],"# TODO\n\n## Admin Interface Cleanup\n\n- [x] Clean up the admin interface.\n\n## Student Submission UX\n\n- [x] Improve the submit experience: block repeated clicks while submitting and show a clear success message after a correct submission.\n\n## Capacity Overview\n\n- [x] Show available project capacity per timeslot on the parent proposals overview and admin page.\n\n## Feedback Notes\n\n- Children currently can submit multiple times; one person reported having to delete duplicate submissions because some children submitted five to eight times.\n- Parent project entry should be made more precise so parents understand better what information is needed.\n- In the project overview, it would be helpful to show the names of the people offering each project.\n- It would be helpful to have an overview of total available capacity: how many children can be assigned to projects overall.\n- It would be helpful to see available project capacity per timeslot.\n- The student entry flow worked well: children were able to submit within one day, and the process also supported reading and writing practice.\n- Assignment and printing worked well and saved time.\n- The biggest remaining operational challenge is finding enough parents who can offer projects.\n- There is a consideration to run only one Projektwoche per year.\n",[],[396],"f7d03416-5d88-11f1-b3b4-1607ee4eb77e","README.md","019e8205-0429-72dd-a700-89aff837c679",["D",1780297827276],"# Projektauswahl System\n\nA dynamic project selection system where students can rank their preferences for different time slots with a comprehensive admin interface for management.\n\n## Features\n\n- **Dynamic Data Management**: Timeslots and projects are stored in SQLite database\n- **Student Interface**: Drag-and-drop interface for ranking project preferences\n- **Advanced Admin Panel**: Web-based interface with inline editing capabilities\n- **Data Export**: CSV export of student responses\n- **Responsive Design**: Works on desktop and mobile devices\n\n## Structure\n\n```\n├── backend/\n│ └── index.ts # Main backend with API routes and admin panel\n├── schueler.html # Student-facing form (dynamically loads data)\n└── README.md # This file\n```\n\n## Usage\n\n### Student Interface\n- Visit the main page to fill out project preferences\n- Enter your name and drag projects to rank them for each timeslot\n- Submit to save responses to database\n\n### Admin Interface\n- Visit `/admin` to manage the system\n- **Inline Editing**: Click \"Edit\" on any timeslot or project to modify it directly in the table\n - Edit timeslot titles, descriptions, and order\n - Edit project names, descriptions, and reassign to different timeslots\n - Visual feedback with highlighted rows during editing\n - Save/Cancel options for each edit operation\n- **Bulk Operations**: Add new timeslots and projects using the forms\n- **Status Management**: Activate/deactivate timeslots and projects\n- **Data Management**: View all student responses and export as CSV\n- **Safe Deletion**: Delete items with confirmation dialogs\n\n## API Endpoints\n\n### Public Endpoints\n- `GET /` - Student form\n- `GET /api/timeslots` - Get all active timeslots with projects\n- `POST /api/responses` - Submit student responses\n\n### Admin Endpoints\n- `GET /admin` - Admin panel interface with inline editing\n- `GET /admin/responses` - View student responses grouped by student\n- `GET /api/debug/data` - View all database data\n- `GET /api/debug/reset` - Reset database (development only)\n- `POST /api/admin/timeslots` - Add new timeslot\n- `POST /api/admin/projects` - Add new project\n- `POST /api/admin/projects/:id/copy` - Copy project to different timeslot\n- `PUT /api/admin/timeslots/:id` - Update timeslot (supports full updates and status toggle)\n- `PUT /api/admin/projects/:id` - Update project (supports full updates and status toggle)\n- `DELETE /api/admin/timeslots/:id` - Delete timeslot (cascades to projects and responses)\n- `DELETE /api/admin/projects/:id` - Delete project\n- `DELETE /api/admin/responses/student/:studentName` - Delete all responses for a specific student\n- `GET /api/admin/export-csv` - Export responses as CSV\n\n## Database Schema\n\n### Timeslots Table\n- `id` - Primary key\n- `title` - Display title (e.g., \"1. Dienstag 9:00-10:30 Uhr\")\n- `time_description` - Time description\n- `order_index` - Display order\n- `active` - Whether timeslot is active\n- `created_at` - Creation timestamp\n\n### Projects Table\n- `id` - Primary key\n- `timeslot_id` - Foreign key to timeslots\n- `project_name` - Project name\n- `project_description` - Optional description\n- `max_participants` - Maximum number of participants (optional)\n- `active` - Whether project is active\n- `created_at` - Creation timestamp\n\n### Responses Table\n- `id` - Primary key\n- `student_name` - Student's name\n- `timeslot_id` - Foreign key to timeslots\n- `first_choice` - First preference\n- `second_choice` - Second preference\n- `third_choice` - Third preference\n- `submitted_at` - Submission timestamp\n\n## Admin Panel Features\n\n### Inline Editing\n- **Timeslots**: Edit title, description, and order index directly in the table\n- **Projects**: Edit name, description, max participants, and reassign to different timeslots\n- **Visual Feedback**: Rows highlight in yellow during edit mode\n- **State Management**: Only one item can be edited at a time\n- **Validation**: Form validation before saving changes\n\n### User Interface\n- **Color-coded Buttons**:\n - 🔵 Edit (Blue) - Start inline editing\n - 🟢 Save (Green) - Confirm changes\n - ⚫ Cancel (Gray) - Discard changes\n - 🔵 Copy (Cyan) - Copy project to another timeslot\n - 🟡 Toggle (Yellow) - Activate/Deactivate\n - 🔴 Delete (Red) - Remove item\n- **Responsive Tables**: Optimized for both desktop and mobile viewing\n- **Real-time Updates**: Changes reflect immediately after saving\n\n### Data Management\n- **Student Response Grouping**: View all responses grouped by student at `/admin/responses`\n- **Student Response Deletion**: Delete all responses for a specific student with one click\n- **Export Functionality**: Download all student responses as CSV\n- **Copy Projects**: Easily duplicate projects across different timeslots\n- **Bulk Operations**: Add multiple items using the forms\n- **Safe Deletion**: Confirmation dialogs prevent accidental deletions\n- **Cascade Operations**: Deleting timeslots removes associated projects and responses\n\n## Default Data\n\nThe system initializes with:\n- 3 timeslots (Tuesday morning sessions)\n- 8 projects (Projekt A through H) for each timeslot\n\n## Customization\n\nYou can customize the system by:\n1. **Using the Admin Panel**: \n - Inline edit existing timeslots and projects\n - Add new timeslots and projects via forms\n - Activate/deactivate items as needed\n2. **Styling Changes**: Modify the CSS in `schueler.html` for student interface styling\n3. **Database Schema**: Update the schema in `backend/index.ts` for additional fields\n4. **Admin Interface**: Customize the admin panel styling and functionality\n\n## Development\n\n### Database Reset\nTo reset the database during development:\n```\nGET /api/debug/reset\n```\nThis will drop all tables and recreate them with default data.\n\n### Debugging\n- Use `/api/debug/data` to view all database contents\n- Check browser console for client-side errors\n- Server logs show database operations and API calls\n\n## Security Notes\n\n- No authentication is currently implemented on admin endpoints\n- Consider adding authentication for production use\n- All admin functions are accessible via `/admin` URL\n- Database operations include proper error handling and validation",[],[404],"f7cffbb8-5d88-11f1-b3b4-1607ee4eb77e","PARENT_PROJECT_SUBMISSIONS_SPEC.md","019e8205-0429-72dd-a700-84dfd814bf95",["D",1780297827276],"# Parent Project Submissions Spec\n\n## Goal\n\nAllow parents to propose Projektwoche projects directly, while keeping admin review lightweight and preserving the current student ranking and assignment workflow.\n\nThis spec does not require implementation yet. It defines the recommended product behavior, data to collect, and likely extension points in the current app.\n\n## Summary\n\nRecommended approach:\n\n- Parents submit project proposals into a separate proposal queue.\n- Admins review proposals with minimal work.\n- Only approved proposals become live projects visible to students.\n- Parents indicate availability, not exact placement.\n- Projects may span multiple consecutive timeslots.\n- A 2-timeslot project means the same children attend both timeslots in order.\n\n## Why Separate Proposals From Live Projects\n\nDo not write parent submissions directly into the live `project_options` table.\n\nReasons:\n\n- Parent submissions will often be incomplete or inconsistent.\n- Admins need to place projects into the timetable based on overall availability.\n- Some projects will need editing before they are suitable for student-facing display.\n- Multi-timeslot projects need scheduling logic before they can be shown to children.\n\nRecommended flow:\n\n1. Parent submits a proposal.\n2. Admin reviews it in a queue.\n3. Admin approves, edits, or rejects it.\n4. Approval creates the actual scheduled project records used by the existing app.\n\n## Parent Submission Data\n\n### Required\n\n- Parent name\n- Email address\n- Project title\n- Short public description\n- Maximum number of children\n- Age suitability\n- Availability across timeslots\n- Project duration in timeslots, default `1`\n\n### Strongly recommended\n\n- Phone number\n- Materials children should bring\n- Indoor / outdoor / either\n- Space or room requirements\n- Materials provided by parent\n- Optional co-facilitator / second adult\n- Notes for admins\n\n### Optional but useful later\n\n- Minimum number of children\n- Setup time needed\n- Cleanup time needed\n- Safety considerations\n- Accessibility notes\n- Whether the project can be repeated for another group\n\n## Proposed Parent-Facing Field Definitions\n\n- `parent_name`: text, required\n- `parent_email`: email, required\n- `parent_phone`: text, optional\n- `project_title`: text, required\n- `project_description`: long text, required\n- `co_facilitators`: text, optional\n- `max_participants`: integer, required\n- `min_participants`: integer, optional\n- `age_group`: enum or multi-select, required\n- `age_group_notes`: text, optional\n- `materials_to_bring`: long text, optional\n- `materials_provided`: long text, optional\n- `location_type`: enum `indoor | outdoor | either`, optional\n- `room_requirements`: long text, optional\n- `availability_timeslot_ids`: list of timeslot ids, required\n- `duration_slots`: integer, required, default `1`\n- `admin_notes_from_parent`: long text, optional\n\n## Age Groups\n\nKeep age groups open-ended.\n\nDo not hardcode only the current school-specific labels yet, because there may be one or two more groups later.\n\nRecommended approach:\n\n- store age groups in configurable data rather than fixed code enums\n- allow multiple selectable age-group options per project if needed\n- preserve an optional free-text note for exceptions or mixed groups\n\nCurrent examples:\n\n- `Delfine` = Klasse 1-3\n- `Drachen` = Klasse 4-6\n- `7/8` = Klasse 7-8\n- `9/10` = Klasse 9-10\n\nPractical consequence:\n\n- the parent form should read age-group options from configurable data\n- the admin review flow should tolerate changes to the age taxonomy without schema rewrites\n\nRecommended configurable structure:\n\n- `id`\n- `label`\n- `min_class`\n- `max_class`\n- `sort_order`\n- `active`\n\nInitial values:\n\n- `delfine`, `Delfine`, `1`, `3`\n- `drachen`, `Drachen`, `4`, `6`\n- `7-8`, `7/8`, `7`, `8`\n- `9-10`, `9/10`, `9`, `10`\n\n## Availability And Scheduling Rules\n\nParents should mark availability only.\n\nAdmins choose the actual scheduled start slot.\n\nRules:\n\n- A proposal can list multiple available timeslots.\n- `duration_slots = 1` means the project occupies one timeslot.\n- `duration_slots = 2` means the project occupies two consecutive timeslots.\n- A 2-slot project is one continuous project for the same children.\n- The second slot is not assigned independently.\n\nValidation rules for duration `2`:\n\n- Only allow approval into a start slot if the next consecutive timeslot exists.\n- Both timeslots must be included in the parent’s availability.\n- Once approved, both slots are reserved together.\n\n## Recommended Data Model\n\nAdd a proposal layer instead of overloading existing tables.\n\n### New table: `project_proposals`\n\nSuggested fields:\n\n- `id`\n- `parent_name`\n- `parent_email`\n- `parent_phone`\n- `project_title`\n- `project_description`\n- `co_facilitators`\n- `max_participants`\n- `min_participants`\n- `age_group`\n- `age_group_notes`\n- `materials_to_bring`\n- `materials_provided`\n- `location_type`\n- `room_requirements`\n- `duration_slots`\n- `admin_notes_from_parent`\n- `review_status`\n- `admin_review_notes`\n- `approved_start_timeslot_id`\n- `created_at`\n- `updated_at`\n\nRecommended `review_status` values:\n\n- `pending`\n- `approved`\n- `rejected`\n- `archived`\n\n### New table: `project_proposal_availability`\n\nSuggested fields:\n\n- `id`\n- `proposal_id`\n- `timeslot_id`\n\nThis normalizes availability rather than storing it as text or JSON.\n\n## How Approved Proposals Become Live Projects\n\nApproval should create scheduled projects in the existing live project model.\n\n### Short-term compatibility approach\n\nKeep the current student and assignment system mostly intact:\n\n- On approval of a 1-slot proposal, create one record in `project_options`.\n- On approval of a 2-slot proposal, create one record per occupied timeslot in `project_options`.\n- Mark those created records as linked to the same underlying proposal.\n\nFor that, add a lightweight linking field to `project_options`, for example:\n\n- `proposal_id`\n- `project_group_id` or `multi_slot_group_id`\n- `slot_index_within_group`\n\nThis keeps backward compatibility while giving the app enough information to treat multi-slot projects as one offering.\n\n### Longer-term cleaner approach\n\nIntroduce a first-class scheduled project entity:\n\n- one scheduled project\n- many occupied timeslots\n- many linked live choices\n\nThis is cleaner, but not required for a first iteration.\n\n## Student Ranking Behavior\n\nThis needs explicit product behavior before implementation.\n\nRecommended behavior:\n\n- A multi-slot project should be shown once, at its start slot.\n- The UI must clearly indicate that it occupies the next slot too.\n- If a child ranks that project, the following slot becomes unavailable for a separate project.\n\nImplication:\n\n- The current response model is timeslot-centric, so multi-slot choices will require either:\n - special submission logic in the student form, or\n - a translation layer that writes linked responses consistently\n\n## Assignment Behavior\n\nFor approved 2-slot projects:\n\n- Assignment must happen as one block.\n- A child assigned to the project in slot 1 is automatically assigned in slot 2.\n- Capacity applies to the full 2-slot block, not independently per slot.\n- Manual reassignment tools must preserve that linkage.\n\nThis is the part most likely to require actual changes to the current assignment UI and persistence.\n\n## Admin Review Workflow\n\nThe review UI should be intentionally small.\n\nRecommended actions on each proposal:\n\n- `Approve`\n- `Edit and approve`\n- `Reject`\n- `Archive`\n\nRecommended review screen columns:\n\n- Parent name\n- Project title\n- Duration\n- Max participants\n- Age group\n- Availability summary\n- Status\n- Quick actions\n\nRecommended approval flow:\n\n1. Admin opens proposal.\n2. Admin chooses a start timeslot from valid available options.\n3. Admin optionally edits display text.\n4. Admin approves.\n5. System creates live project records and links them back to the proposal.\n\n## Minimal Viable Version\n\nPhase 1 should aim for low complexity:\n\n- Parent proposal form\n- Proposal storage\n- Admin review queue\n- Approve into a scheduled live project\n- Support for duration `1` and `2`\n- No parent editing after submission\n- No draft saving\n- No automatic email notifications\n\n## Suggested Phased Rollout\n\n### Phase 1\n\n- Add proposal intake\n- Add review queue\n- Add approval into existing live project structure\n- Support duration `1` and `2`\n\n### Phase 2\n\n- Improve multi-slot student ranking UX\n- Make assignment UI block-aware for linked timeslots\n- Add validation around consecutive-slot occupancy\n\n### Phase 3\n\n- Parent edits after submission\n- Email confirmation\n- Duplicate/repeat project support\n- Better scheduling assistance for admins\n\n## Google Form Alternative\n\nGoogle Forms is viable for intake, but it is weaker as the long-term solution.\n\n### Pros\n\n- Very fast to set up\n- Familiar to parents\n- No implementation needed for the first collection round\n\n### Cons\n\n- Harder to validate structured constraints like multi-slot availability\n- Harder to keep age groups and timeslots in sync with the app\n- Review and approval become manual copy/paste work\n- Multi-slot project logic will live outside the app\n- Changes to available timeslots require form maintenance in two places\n\n### Recommendation\n\nIf you need something immediately for a one-off round, Google Forms is acceptable.\n\nIf you expect this to become part of the regular Projektwoche workflow, build it into the app. The admin review requirement and the need for multi-timeslot scheduling both argue strongly for native support.\n\n## Open Questions\n\n- What is the final label for the age group above `Drachen`?\n- Should one project ever be repeatable with different children in multiple separate slot blocks?\n- Do you want a hard cap on duration at `2`, or should the model allow more later?\n- Should parents see a confirmation summary after submission?\n- Should admin approval create live projects immediately, or leave them inactive by default until published?\n\n## Recommendation\n\nBuild this into the app rather than relying on Google Forms, unless you need a stopgap this week.\n\nThe simplest robust design is:\n\n- separate proposal queue\n- admin approval\n- parent availability, not parent slot choice\n- explicit duration field\n- linked handling for 2-slot projects\n",[],[411],"f7cfd16a-5d88-11f1-b3b4-1607ee4eb77e","AGENTS.md","019e8205-0429-72dd-a700-81c0b5556f8d",["D",1780297827276],"# AGENTS\n\n## Project Inventory\n\nThis repository is a Val Town app for managing a school \"Projektwoche\" workflow.\n\nIt has two main user roles:\n\n- Students submit ranked project preferences for each timeslot.\n- Admins manage timeslots and parent-offered projects, inspect submissions, and assign students to projects.\n\nThe live backend is implemented in [backend/index.ts](/Users/chris/fnifs/Projektwoche/backend/index.ts). It uses:\n\n- `Hono` for routing\n- Val Town `sqlite` for persistence\n- `readFile(..., import.meta.url)` to serve static HTML pages from the repo\n\nThere is no separate frontend build step in this repo. The UI is plain HTML/CSS/JS files served directly by the backend.\n\n## Runtime And Hosting\n\n- Host platform: Val Town\n- Local Val Town metadata: [.vt/state.json](/Users/chris/fnifs/Projektwoche/.vt/state.json)\n- Primary backend entrypoint: [backend/index.ts](/Users/chris/fnifs/Projektwoche/backend/index.ts)\n- [main.ts](/Users/chris/fnifs/Projektwoche/main.ts) is currently empty and appears unused\n\nIf you change routes or the HTML filenames, update `readFile(...)` calls and route handlers in `backend/index.ts` together.\n\n## What The App Does\n\n### Domain model\n\n- A \"Projektwoche\" consists of multiple timeslots.\n- Projects are offered by parents; this is represented in the backend via the `offered_by` field on projects.\n- Some projects may span two timeslots. In practice, the app supports this by duplicating or copying a project into multiple timeslots rather than by storing a dedicated multi-slot project entity.\n- Children rank their preferred projects within each timeslot.\n- Admins then assign children to projects, aiming to satisfy the highest-ranked preferences where capacity and constraints allow.\n\n### Student flow\n\n- `GET /` serves [schueler.html](/Users/chris/fnifs/Projektwoche/schueler.html)\n- The page loads active timeslots and their active projects from `GET /api/timeslots`\n- Students submit ranked preferences to `POST /api/responses`\n- Each submission stores one response row per timeslot, linked by a shared `submission_id`\n\n### Admin flow\n\n- `GET /admin` serves [admin.html](/Users/chris/fnifs/Projektwoche/admin.html)\n- Admins can create, edit, activate/deactivate, copy, and delete timeslots and projects\n- Admins can inspect raw response data and export CSV\n- Admins can compute and manually adjust assignments, then save them per timeslot\n- The project-copy workflow is the current mechanism for representing projects that run across more than one timeslot\n\n### Assignment flow\n\nAssignments are a second-stage workflow after students submit preferences:\n\n- [admin-assignments.html](/Users/chris/fnifs/Projektwoche/admin-assignments.html) optimizes assignments for a selected timeslot and allows drag/drop manual correction\n- Saved assignments are stored in the `project_assignments` table\n- [admin-assignments-individual.html](/Users/chris/fnifs/Projektwoche/admin-assignments-individual.html) shows each student’s schedule across timeslots\n- [admin-assignments-by-project.html](/Users/chris/fnifs/Projektwoche/admin-assignments-by-project.html) shows rosters grouped by project\n- The optimizer tries to place children into preferred projects first, but final assignments can be adjusted manually by admins\n\n## File Inventory\n\n- [backend/index.ts](/Users/chris/fnifs/Projektwoche/backend/index.ts): server routes, DB schema, migrations, CSV export, static page serving\n- [schueler.html](/Users/chris/fnifs/Projektwoche/schueler.html): student submission interface\n- [admin.html](/Users/chris/fnifs/Projektwoche/admin.html): admin CRUD page for timeslots and projects\n- [admin-responses.html](/Users/chris/fnifs/Projektwoche/admin-responses.html): grouped submission review and deletion UI\n- [admin-assignments.html](/Users/chris/fnifs/Projektwoche/admin-assignments.html): assignment optimizer and manual adjustment UI\n- [admin-assignments-individual.html](/Users/chris/fnifs/Projektwoche/admin-assignments-individual.html): per-student assignment view\n- [admin-assignments-by-project.html](/Users/chris/fnifs/Projektwoche/admin-assignments-by-project.html): per-project assignment view\n- [assignment.html](/Users/chris/fnifs/Projektwoche/assignment.html): standalone assignment optimizer prototype/tool; it is not served by `backend/index.ts`\n- [README.md](/Users/chris/fnifs/Projektwoche/README.md): partially outdated overview\n\n## API Inventory\n\n### Public routes\n\n- `GET /`\n- `GET /api/timeslots`\n- `POST /api/responses`\n\n### Admin pages\n\n- `GET /admin`\n- `GET /admin/responses`\n- `GET /admin/assignments`\n- `GET /admin/assignments/individual`\n- `GET /admin/assignments/by-project`\n\n### Admin data routes\n\n- `GET /api/debug/data`\n- `GET /api/debug/reset`\n- `POST /api/admin/timeslots`\n- `POST /api/admin/projects`\n- `POST /api/admin/projects/:id/copy`\n- `PUT /api/admin/timeslots/:id`\n- `PUT /api/admin/projects/:id`\n- `DELETE /api/admin/timeslots/:id`\n- `DELETE /api/admin/projects/:id`\n- `DELETE /api/admin/responses/student/:studentName`\n- `DELETE /api/admin/responses/submission/:submissionId`\n- `GET /api/admin/export-csv`\n\n### Assignment routes\n\n- `POST /api/admin/assignments/:timeslotId/save`\n- `POST /api/admin/assignments/:timeslotId/assign`\n- `GET /api/admin/assignments/:timeslotId/load`\n- `DELETE /api/admin/assignments/:timeslotId`\n\n## Database Inventory\n\nTables created in `initDatabase()`:\n\n- `project_timeslots`\n- `project_options`\n- `student_responses`\n- `project_assignments`\n\nImportant schema details:\n\n- `project_options` includes migrated columns `offered_by` and `what_to_bring`\n- `student_responses` stores `submission_id`, so one student submission spans multiple rows\n- `project_assignments` has a uniqueness constraint on `(timeslot_id, student_name)`\n\n## Important Behaviors And Gotchas\n\n- The README no longer reflects the full system. Assignments, `offered_by`, `what_to_bring`, and submission deletion are implemented in code but not fully documented there.\n- There is no auth. All admin pages and admin APIs are publicly reachable if the Val is public.\n- `GET /api/debug/reset` drops tables and reseeds defaults. Treat it as destructive.\n- `GET /api/debug/data` exposes the full data model and is used heavily by the admin pages.\n- The root page injects `window.DYNAMIC_DATA_ENDPOINT` and `window.SUBMIT_ENDPOINT` into `schueler.html` at request time.\n- Default seed data is placeholder content for three Tuesday timeslots and projects A-H.\n- `assignment.html` duplicates assignment logic but is currently separate from the served admin workflow.\n- Two-timeslot projects are currently modeled operationally by copying the same project into multiple timeslots, which means there is no built-in guarantee that those linked entries stay synchronized.\n\n## Editing Guidance\n\nWhen changing this project:\n\n- Keep backend route names and frontend `fetch(...)` calls aligned.\n- Preserve the JSON shapes expected by the HTML pages before refactoring API responses.\n- If you change database columns, update:\n - table creation in `initDatabase()`\n - migration checks in `initDatabase()`\n - CRUD SQL\n - any affected admin or student HTML pages\n- If you introduce first-class support for multi-timeslot projects, review both the submission model and assignment persistence carefully; the current schema is timeslot-centric.\n- If you change how student submissions work, account for the `submission_id` grouping logic used in the admin response pages.\n- If you change assignment persistence, update all three assignment-related HTML pages, not just `admin-assignments.html`.\n\n## Recommended Next Cleanup\n\n- Update [README.md](/Users/chris/fnifs/Projektwoche/README.md) to match the actual current feature set\n- Add auth if this app is intended for real use on a public Val\n- Remove or explicitly document whether [assignment.html](/Users/chris/fnifs/Projektwoche/assignment.html) should remain as a standalone utility\n",[],[418],"f7cfcfd0-5d88-11f1-b3b4-1607ee4eb77e",".vtignore","019e8205-0429-72dd-a700-7fac49f61ea2",["D",1780297827276],".git\n.DS_Store\n.claude\n",[],[425],"f7cfaa96-5d88-11f1-b3b4-1607ee4eb77e","youtube-dfNdxB4Giyo","019e8205-0429-72dd-a700-772885569e5e","019e8205-0429-72dd-a700-7814f159de1c",["D",1780297827276],[],[438,432],"slides","f7cfce36-5d88-11f1-b3b4-1607ee4eb77e",["D",1780297827276],[282],[438],["D",1780300369485],[],[18,71],["D",1780297827276],[280],[18],"9f47efd8-5d8c-11f1-aa85-1607ee4eb77e","extensions.json","9f47f082-5d8c-11f1-aa85-1607ee4eb77e","9f1c09fe-5d8c-11f1-bf5a-1607ee4eb77e",["D",1780299397414],"{\n \"recommendations\": [\n \"denoland.vscode-deno\"\n ]\n}",[],[457,450],".vscode","9f1c0922-5d8c-11f1-bf5a-1607ee4eb77e",["D",1780299397131],[278],[457],"f7cefe98-5d88-11f1-b3b4-1607ee4eb77e","019e8205-0429-72dd-a700-65fd279873b6","019e8205-0429-72dd-a700-691af7db742e",["D",1780297827276],"Unnamed repository; edit this file 'description' to name the repository.\n",[],[469,111],".git","f7cefc9a-5d88-11f1-b3b4-1607ee4eb77e","config","019e8205-0429-72dd-a700-6118ab33cd78",["D",1780297827276],"[core]\n\trepositoryformatversion = 0\n\tfilemode = true\n\tbare = false\n\tlogallrefupdates = true\n\tignorecase = true\n\tprecomposeunicode = true\n",[],[469,471],"f7cefb46-5d88-11f1-b3b4-1607ee4eb77e","HEAD","019e8205-0429-72dd-a700-5f9f04497290",["D",1780297827276],"ref: refs/heads/main\n",[],[469,478],"f7cef9e8-5d88-11f1-b3b4-1607ee4eb77e","COMMIT_EDITMSG","019e8205-0429-72dd-a700-595e5b7cf406",["D",1780297827276],"Initial commit\n",[],[469,485],"f7cef74a-5d88-11f1-b3b4-1607ee4eb77e","tags","019e8205-0429-72dd-a700-516e5c5e546b","019e8205-0429-72dd-a700-549992068d33",["D",1780297827276],[],[469,498,492],"refs","f7cef452-5d88-11f1-b3b4-1607ee4eb77e","019e8205-0429-72dd-a700-4ac5f4e71d6c","019e8205-0429-72dd-a700-4f77c21435ed",["D",1780297827276],"d7e2572b57065f97093f9101ec3de5622abcd797\n",[],[469,498,506,16],"heads","f7cef60a-5d88-11f1-b3b4-1607ee4eb77e",["D",1780297827276],[271],[469,498,506],"f7cef862-5d88-11f1-b3b4-1607ee4eb77e",["D",1780297827276],[270,272],[469,498],"f7cef24a-5d88-11f1-b3b4-1607ee4eb77e","pack","019e8205-0429-72dd-a700-406d3aece9a4","019e8205-0429-72dd-a700-45d7905f9302",["D",1780297827276],[],[469,522,516],"objects","f7cef146-5d88-11f1-b3b4-1607ee4eb77e","info","019e8205-0429-72dd-a700-3f1023372258",["D",1780297827276],[],[469,522,524],"f7cef042-5d88-11f1-b3b4-1607ee4eb77e","ff","019e8205-0429-72dd-a700-38f8a3cb80b8",["D",1780297827276],[],[469,522,530],"f7ceef34-5d88-11f1-b3b4-1607ee4eb77e","f7","019e8205-0429-72dd-a700-37b4b29b5953",["D",1780297827276],[],[469,522,536],"f7ceee1c-5d88-11f1-b3b4-1607ee4eb77e","e8","019e8205-0429-72dd-a700-307d272123c0",["D",1780297827276],[],[469,522,542],"f7ceecfa-5d88-11f1-b3b4-1607ee4eb77e","e6","019e8205-0429-72dd-a700-2f14826c2789",["D",1780297827276],[],[469,522,548],"f7ceec00-5d88-11f1-b3b4-1607ee4eb77e","d7","019e8205-0429-72dd-a700-2925d6f1ed60",["D",1780297827276],[],[469,522,554],"f7ceeafc-5d88-11f1-b3b4-1607ee4eb77e","d3","019e8205-0429-72dd-a700-2699b5fab04f",["D",1780297827276],[],[469,522,560],"f7cee9e4-5d88-11f1-b3b4-1607ee4eb77e","ab","019e8205-0429-72dd-a700-20a7705e9a2e",["D",1780297827276],[],[469,522,566],"f7cee8cc-5d88-11f1-b3b4-1607ee4eb77e","a2","019e8205-0429-72dd-a700-1ce149172e00",["D",1780297827276],[],[469,522,572],"f7cee7b4-5d88-11f1-b3b4-1607ee4eb77e","92","019e8205-0429-72dd-a700-1896f9dd8a4a",["D",1780297827276],[],[469,522,578],"f7cee6a6-5d88-11f1-b3b4-1607ee4eb77e","8f","019e8205-0429-72dd-a700-14c220eae4c9",["D",1780297827276],[],[469,522,584],"f7cee584-5d88-11f1-b3b4-1607ee4eb77e","8e","019e8205-0429-72dd-a700-1268a1580293",["D",1780297827276],[],[469,522,590],"f7cee3fe-5d88-11f1-b3b4-1607ee4eb77e","87","019e8205-0429-72dd-a700-0f5c93f8a372",["D",1780297827276],[],[469,522,596],"f7cee2fa-5d88-11f1-b3b4-1607ee4eb77e","83","019e8205-0429-72dd-a700-0abe9b39054e",["D",1780297827276],[],[469,522,602],"f7cee1ec-5d88-11f1-b3b4-1607ee4eb77e","81","019e8205-0429-72dd-a700-072e711e7f2e",["D",1780297827276],[],[469,522,608],"f7cee0d4-5d88-11f1-b3b4-1607ee4eb77e","6a","019e8205-0429-72dd-a700-0333389e87d4",["D",1780297827276],[],[469,522,614],"f7cedfbc-5d88-11f1-b3b4-1607ee4eb77e","68","019e8205-0429-72dd-a6ff-fc72a2668ce9",["D",1780297827276],[],[469,522,620],"f7cede68-5d88-11f1-b3b4-1607ee4eb77e","67","019e8205-0429-72dd-a6ff-f888318cd97e",["D",1780297827276],[],[469,522,626],"f7cedd14-5d88-11f1-b3b4-1607ee4eb77e","63","019e8205-0429-72dd-a6ff-f676392d6eb1",["D",1780297827276],[],[469,522,632],"f7cedb48-5d88-11f1-b3b4-1607ee4eb77e","61","019e8205-0429-72dd-a6ff-f08f64260cdf",["D",1780297827276],[],[469,522,638],"f7ced422-5d88-11f1-b3b4-1607ee4eb77e","55","019e8205-0429-72dd-a6ff-ee63048f70ea",["D",1780297827276],[],[469,522,644],"f7ced13e-5d88-11f1-b3b4-1607ee4eb77e","53","019e8205-0429-72dd-a6ff-eb48885ca22f",["D",1780297827276],[],[469,522,650],"f7cecfae-5d88-11f1-b3b4-1607ee4eb77e","4e","019e8205-0429-72dd-a6ff-e483f4176aaf",["D",1780297827276],[],[469,522,656],"f7cece28-5d88-11f1-b3b4-1607ee4eb77e","4b","019e8205-0429-72dd-a6ff-e2175fc8c159",["D",1780297827276],[],[469,522,662],"f7cecca2-5d88-11f1-b3b4-1607ee4eb77e","49","019e8205-0429-72dd-a6ff-dfd57d46cb34",["D",1780297827276],[],[469,522,668],"f7cecb1c-5d88-11f1-b3b4-1607ee4eb77e","47","019e8205-0429-72dd-a6ff-da27176297e2",["D",1780297827276],[],[469,522,674],"f7cec964-5d88-11f1-b3b4-1607ee4eb77e","45","019e8205-0429-72dd-a6ff-d4790c008c1c",["D",1780297827276],[],[469,522,680],"f7cec3e2-5d88-11f1-b3b4-1607ee4eb77e","42","019e8205-0429-72dd-a6ff-d3eb5a7f2cc2",["D",1780297827276],[],[469,522,686],"f7cec1b2-5d88-11f1-b3b4-1607ee4eb77e","3c","019e8205-0429-72dd-a6ff-ce03928c6928",["D",1780297827276],[],[469,522,692],"f7cec022-5d88-11f1-b3b4-1607ee4eb77e","29","019e8205-0429-72dd-a6ff-cbfc0448f258",["D",1780297827276],[],[469,522,698],"f7cebea6-5d88-11f1-b3b4-1607ee4eb77e","21","019e8205-0429-72dd-a6ff-c5db25b5f0a3",["D",1780297827276],[],[469,522,704],"f7cebcee-5d88-11f1-b3b4-1607ee4eb77e","1a","019e8205-0429-72dd-a6ff-c16157b96f5c",["D",1780297827276],[],[469,522,710],"f7ceb4d8-5d88-11f1-b3b4-1607ee4eb77e","02","019e8205-0429-72dd-a6ff-becab5830151",["D",1780297827276],[],[469,522,716],"f7cef34e-5d88-11f1-b3b4-1607ee4eb77e",["D",1780297827276],[235,236,237,238,239,240,241,242,243,244,245,246,247,248,249,250,251,252,253,254,255,256,257,258,259,260,261,262,263,264,265,266,267,268],[469,522],"f7ceaf88-5d88-11f1-b3b4-1607ee4eb77e","019e8205-0429-72dd-a6ff-b69a321f3ea3","019e8205-0429-72dd-a6ff-baad4e5d8435",["D",1780297827276],"0000000000000000000000000000000000000000 d7e2572b57065f97093f9101ec3de5622abcd797 Chris Eidhof 1776948695 +0200\tcommit (initial): Initial commit\n",[],[469,732,478],"logs","f7cea9b6-5d88-11f1-b3b4-1607ee4eb77e","019e8205-0428-7440-918e-3b21e91886db","019e8205-0429-72dd-a6ff-ae8506fb10b4",["D",1780297827276],[],[469,732,498,506,16],"f7ceac7c-5d88-11f1-b3b4-1607ee4eb77e","019e8205-0429-72dd-a6ff-b00a67df8033",["D",1780297827276],[232],[469,732,498,506],"f7ceae0c-5d88-11f1-b3b4-1607ee4eb77e",["D",1780297827276],[231],[469,732,498],"f7ceb30c-5d88-11f1-b3b4-1607ee4eb77e",["D",1780297827276],[230,233],[469,732],"f7cea3c6-5d88-11f1-b3b4-1607ee4eb77e","exclude","019e8205-0428-7440-918e-32e191618a7d","019e8205-0428-7440-918e-35977c74a7c9",["D",1780297827276],"# git ls-files --others --exclude-from=.git/info/exclude\n# Lines that start with '#' are comments.\n# For a project mostly in C, the following would be a good set of\n# exclude patterns (uncomment them if you want to use them):\n# *.[oa]\n# *~\n",[],[469,524,753],"f7cea7e0-5d88-11f1-b3b4-1607ee4eb77e",["D",1780297827276],[228],[469,524],"f7ce8184-5d88-11f1-b3b4-1607ee4eb77e","update.sample","019e8205-0428-7440-918e-28c04212f67d","019e8205-0428-7440-918e-2c4071bf00bd",["D",1780297827276],"#!/bin/sh\n#\n# An example hook script to block unannotated tags from entering.\n# Called by \"git receive-pack\" with arguments: refname sha1-old sha1-new\n#\n# To enable this hook, rename this file to \"update\".\n#\n# Config\n# ------\n# hooks.allowunannotated\n# This boolean sets whether unannotated tags will be allowed into the\n# repository. By default they won't be.\n# hooks.allowdeletetag\n# This boolean sets whether deleting tags will be allowed in the\n# repository. By default they won't be.\n# hooks.allowmodifytag\n# This boolean sets whether a tag may be modified after creation. By default\n# it won't be.\n# hooks.allowdeletebranch\n# This boolean sets whether deleting branches will be allowed in the\n# repository. By default they won't be.\n# hooks.denycreatebranch\n# This boolean sets whether remotely creating branches will be denied\n# in the repository. By default this is allowed.\n#\n\n# --- Command line\nrefname=\"$1\"\noldrev=\"$2\"\nnewrev=\"$3\"\n\n# --- Safety check\nif [ -z \"$GIT_DIR\" ]; then\n\techo \"Don't run this script from the command line.\" >&2\n\techo \" (if you want, you could supply GIT_DIR then run\" >&2\n\techo \" $0 )\" >&2\n\texit 1\nfi\n\nif [ -z \"$refname\" -o -z \"$oldrev\" -o -z \"$newrev\" ]; then\n\techo \"usage: $0 \" >&2\n\texit 1\nfi\n\n# --- Config\nallowunannotated=$(git config --type=bool hooks.allowunannotated)\nallowdeletebranch=$(git config --type=bool hooks.allowdeletebranch)\ndenycreatebranch=$(git config --type=bool hooks.denycreatebranch)\nallowdeletetag=$(git config --type=bool hooks.allowdeletetag)\nallowmodifytag=$(git config --type=bool hooks.allowmodifytag)\n\n# check for no description\nprojectdesc=$(sed -e '1q' \"$GIT_DIR/description\")\ncase \"$projectdesc\" in\n\"Unnamed repository\"* | \"\")\n\techo \"*** Project description file hasn't been set\" >&2\n\texit 1\n\t;;\nesac\n\n# --- Check types\n# if $newrev is 0000...0000, it's a commit to delete a ref.\nzero=$(git hash-object --stdin &2\n\t\t\techo \"*** Use 'git tag [ -a | -s ]' for tags you want to propagate.\" >&2\n\t\t\texit 1\n\t\tfi\n\t\t;;\n\trefs/tags/*,delete)\n\t\t# delete tag\n\t\tif [ \"$allowdeletetag\" != \"true\" ]; then\n\t\t\techo \"*** Deleting a tag is not allowed in this repository\" >&2\n\t\t\texit 1\n\t\tfi\n\t\t;;\n\trefs/tags/*,tag)\n\t\t# annotated tag\n\t\tif [ \"$allowmodifytag\" != \"true\" ] && git rev-parse $refname > /dev/null 2>&1\n\t\tthen\n\t\t\techo \"*** Tag '$refname' already exists.\" >&2\n\t\t\techo \"*** Modifying a tag is not allowed in this repository.\" >&2\n\t\t\texit 1\n\t\tfi\n\t\t;;\n\trefs/heads/*,commit)\n\t\t# branch\n\t\tif [ \"$oldrev\" = \"$zero\" -a \"$denycreatebranch\" = \"true\" ]; then\n\t\t\techo \"*** Creating a branch is not allowed in this repository\" >&2\n\t\t\texit 1\n\t\tfi\n\t\t;;\n\trefs/heads/*,delete)\n\t\t# delete branch\n\t\tif [ \"$allowdeletebranch\" != \"true\" ]; then\n\t\t\techo \"*** Deleting a branch is not allowed in this repository\" >&2\n\t\t\texit 1\n\t\tfi\n\t\t;;\n\trefs/remotes/*,commit)\n\t\t# tracking branch\n\t\t;;\n\trefs/remotes/*,delete)\n\t\t# delete tracking branch\n\t\tif [ \"$allowdeletebranch\" != \"true\" ]; then\n\t\t\techo \"*** Deleting a tracking branch is not allowed in this repository\" >&2\n\t\t\texit 1\n\t\tfi\n\t\t;;\n\t*)\n\t\t# Anything else (is there anything else?)\n\t\techo \"*** Update hook: unknown type of update to ref $refname of type $newrev_type\" >&2\n\t\texit 1\n\t\t;;\nesac\n\n# --- Finished\nexit 0\n",[],[469,772,765],"hooks","f7ce7022-5d88-11f1-b3b4-1607ee4eb77e","sendemail-validate.sample","019e8205-0428-7440-918e-278cf2d7799a",["D",1780297827276],"#!/bin/sh\n\n# An example hook script to validate a patch (and/or patch series) before\n# sending it via email.\n#\n# The hook should exit with non-zero status after issuing an appropriate\n# message if it wants to prevent the email(s) from being sent.\n#\n# To enable this hook, rename this file to \"sendemail-validate\".\n#\n# By default, it will only check that the patch(es) can be applied on top of\n# the default upstream branch without conflicts in a secondary worktree. After\n# validation (successful or not) of the last patch of a series, the worktree\n# will be deleted.\n#\n# The following config variables can be set to change the default remote and\n# remote ref that are used to apply the patches against:\n#\n# sendemail.validateRemote (default: origin)\n# sendemail.validateRemoteRef (default: HEAD)\n#\n# Replace the TODO placeholders with appropriate checks according to your\n# needs.\n\nvalidate_cover_letter () {\n\tfile=\"$1\"\n\t# TODO: Replace with appropriate checks (e.g. spell checking).\n\ttrue\n}\n\nvalidate_patch () {\n\tfile=\"$1\"\n\t# Ensure that the patch applies without conflicts.\n\tgit am -3 \"$file\" || return\n\t# TODO: Replace with appropriate checks for this patch\n\t# (e.g. checkpatch.pl).\n\ttrue\n}\n\nvalidate_series () {\n\t# TODO: Replace with appropriate checks for the whole series\n\t# (e.g. quick build, coding style checks, etc.).\n\ttrue\n}\n\n# main -------------------------------------------------------------------------\n\nif test \"$GIT_SENDEMAIL_FILE_COUNTER\" = 1\nthen\n\tremote=$(git config --default origin --get sendemail.validateRemote) &&\n\tref=$(git config --default HEAD --get sendemail.validateRemoteRef) &&\n\tworktree=$(mktemp --tmpdir -d sendemail-validate.XXXXXXX) &&\n\tgit worktree add -fd --checkout \"$worktree\" \"refs/remotes/$remote/$ref\" &&\n\tgit config --replace-all sendemail.validateWorktree \"$worktree\"\nelse\n\tworktree=$(git config --get sendemail.validateWorktree)\nfi || {\n\techo \"sendemail-validate: error: failed to prepare worktree\" >&2\n\texit 1\n}\n\nunset GIT_DIR GIT_WORK_TREE\ncd \"$worktree\" &&\n\nif grep -q \"^diff --git \" \"$1\"\nthen\n\tvalidate_patch \"$1\"\nelse\n\tvalidate_cover_letter \"$1\"\nfi &&\n\nif test \"$GIT_SENDEMAIL_FILE_COUNTER\" = \"$GIT_SENDEMAIL_FILE_TOTAL\"\nthen\n\tgit config --unset-all sendemail.validateWorktree &&\n\ttrap 'git worktree remove -ff \"$worktree\"' EXIT &&\n\tvalidate_series\nfi\n",[],[469,772,774],"f7793652-5d88-11f1-b3b4-1607ee4eb77e","push-to-checkout.sample","019e8205-0428-7440-918e-22b6b978e395",["D",1780297827276],"#!/bin/sh\n\n# An example hook script to update a checked-out tree on a git push.\n#\n# This hook is invoked by git-receive-pack(1) when it reacts to git\n# push and updates reference(s) in its repository, and when the push\n# tries to update the branch that is currently checked out and the\n# receive.denyCurrentBranch configuration variable is set to\n# updateInstead.\n#\n# By default, such a push is refused if the working tree and the index\n# of the remote repository has any difference from the currently\n# checked out commit; when both the working tree and the index match\n# the current commit, they are updated to match the newly pushed tip\n# of the branch. This hook is to be used to override the default\n# behaviour; however the code below reimplements the default behaviour\n# as a starting point for convenient modification.\n#\n# The hook receives the commit with which the tip of the current\n# branch is going to be updated:\ncommit=$1\n\n# It can exit with a non-zero status to refuse the push (when it does\n# so, it must not modify the index or the working tree).\ndie () {\n\techo >&2 \"$*\"\n\texit 1\n}\n\n# Or it can make any necessary changes to the working tree and to the\n# index to bring them to the desired state when the tip of the current\n# branch is updated to the new commit, and exit with a zero status.\n#\n# For example, the hook can simply run git read-tree -u -m HEAD \"$1\"\n# in order to emulate git fetch that is run in the reverse direction\n# with git push, as the two-tree form of git read-tree -u -m is\n# essentially the same as git switch or git checkout that switches\n# branches while keeping the local changes in the working tree that do\n# not interfere with the difference between the branches.\n\n# The below is a more-or-less exact translation to shell of the C code\n# for the default behaviour for git's push-to-checkout hook defined in\n# the push_to_deploy() function in builtin/receive-pack.c.\n#\n# Note that the hook will be executed from the repository directory,\n# not from the working tree, so if you want to perform operations on\n# the working tree, you will have to adapt your code accordingly, e.g.\n# by adding \"cd ..\" or using relative paths.\n\nif ! git update-index -q --ignore-submodules --refresh\nthen\n\tdie \"Up-to-date check failed\"\nfi\n\nif ! git diff-files --quiet --ignore-submodules --\nthen\n\tdie \"Working directory has unstaged changes\"\nfi\n\n# This is a rough translation of:\n#\n# head_has_history() ? \"HEAD\" : EMPTY_TREE_SHA1_HEX\nif git cat-file -e HEAD 2>/dev/null\nthen\n\thead=HEAD\nelse\n\thead=$(git hash-object -t tree --stdin \\).*$/Signed-off-by: \\1/p')\n# git interpret-trailers --in-place --trailer \"$SOB\" \"$COMMIT_MSG_FILE\"\n# if test -z \"$COMMIT_SOURCE\"\n# then\n# /usr/bin/perl -i.bak -pe 'print \"\\n\" if !$first_line++' \"$COMMIT_MSG_FILE\"\n# fi\n",[],[469,772,788],"f7792928-5d88-11f1-b3b4-1607ee4eb77e","pre-receive.sample","019e8205-0428-7440-918e-19c410f349a1",["D",1780297827276],"#!/bin/sh\n#\n# An example hook script to make use of push options.\n# The example simply echoes all push options that start with 'echoback='\n# and rejects all pushes when the \"reject\" push option is used.\n#\n# To enable this hook, rename this file to \"pre-receive\".\n\nif test -n \"$GIT_PUSH_OPTION_COUNT\"\nthen\n\ti=0\n\twhile test \"$i\" -lt \"$GIT_PUSH_OPTION_COUNT\"\n\tdo\n\t\teval \"value=\\$GIT_PUSH_OPTION_$i\"\n\t\tcase \"$value\" in\n\t\techoback=*)\n\t\t\techo \"echo from the pre-receive-hook: ${value#*=}\" >&2\n\t\t\t;;\n\t\treject)\n\t\t\texit 1\n\t\tesac\n\t\ti=$((i + 1))\n\tdone\nfi\n",[],[469,772,795],"f7790cc2-5d88-11f1-b3b4-1607ee4eb77e","pre-rebase.sample","019e8205-0428-7440-918e-15f15ee539b6",["D",1780297827276],"#!/bin/sh\n#\n# Copyright (c) 2006, 2008 Junio C Hamano\n#\n# The \"pre-rebase\" hook is run just before \"git rebase\" starts doing\n# its job, and can prevent the command from running by exiting with\n# non-zero status.\n#\n# The hook is called with the following parameters:\n#\n# $1 -- the upstream the series was forked from.\n# $2 -- the branch being rebased (or empty when rebasing the current branch).\n#\n# This sample shows how to prevent topic branches that are already\n# merged to 'next' branch from getting rebased, because allowing it\n# would result in rebasing already published history.\n\npublish=next\nbasebranch=\"$1\"\nif test \"$#\" = 2\nthen\n\ttopic=\"refs/heads/$2\"\nelse\n\ttopic=`git symbolic-ref HEAD` ||\n\texit 0 ;# we do not interrupt rebasing detached HEAD\nfi\n\ncase \"$topic\" in\nrefs/heads/??/*)\n\t;;\n*)\n\texit 0 ;# we do not interrupt others.\n\t;;\nesac\n\n# Now we are dealing with a topic branch being rebased\n# on top of master. Is it OK to rebase it?\n\n# Does the topic really exist?\ngit show-ref -q \"$topic\" || {\n\techo >&2 \"No such branch $topic\"\n\texit 1\n}\n\n# Is topic fully merged to master?\nnot_in_master=`git rev-list --pretty=oneline ^master \"$topic\"`\nif test -z \"$not_in_master\"\nthen\n\techo >&2 \"$topic is fully merged to master; better remove it.\"\n\texit 1 ;# we could allow it, but there is no point.\nfi\n\n# Is topic ever merged to next? If so you should not be rebasing it.\nonly_next_1=`git rev-list ^master \"^$topic\" ${publish} | sort`\nonly_next_2=`git rev-list ^master ${publish} | sort`\nif test \"$only_next_1\" = \"$only_next_2\"\nthen\n\tnot_in_topic=`git rev-list \"^$topic\" master`\n\tif test -z \"$not_in_topic\"\n\tthen\n\t\techo >&2 \"$topic is already up to date with master\"\n\t\texit 1 ;# we could allow it, but there is no point.\n\telse\n\t\texit 0\n\tfi\nelse\n\tnot_in_next=`git rev-list --pretty=oneline ^${publish} \"$topic\"`\n\t/usr/bin/perl -e '\n\t\tmy $topic = $ARGV[0];\n\t\tmy $msg = \"* $topic has commits already merged to public branch:\\n\";\n\t\tmy (%not_in_next) = map {\n\t\t\t/^([0-9a-f]+) /;\n\t\t\t($1 => 1);\n\t\t} split(/\\n/, $ARGV[1]);\n\t\tfor my $elem (map {\n\t\t\t\t/^([0-9a-f]+) (.*)$/;\n\t\t\t\t[$1 => $2];\n\t\t\t} split(/\\n/, $ARGV[2])) {\n\t\t\tif (!exists $not_in_next{$elem->[0]}) {\n\t\t\t\tif ($msg) {\n\t\t\t\t\tprint STDERR $msg;\n\t\t\t\t\tundef $msg;\n\t\t\t\t}\n\t\t\t\tprint STDERR \" $elem->[1]\\n\";\n\t\t\t}\n\t\t}\n\t' \"$topic\" \"$not_in_next\" \"$not_in_master\"\n\texit 1\nfi\n\n<<\\DOC_END\n\nThis sample hook safeguards topic branches that have been\npublished from being rewound.\n\nThe workflow assumed here is:\n\n * Once a topic branch forks from \"master\", \"master\" is never\n merged into it again (either directly or indirectly).\n\n * Once a topic branch is fully cooked and merged into \"master\",\n it is deleted. If you need to build on top of it to correct\n earlier mistakes, a new topic branch is created by forking at\n the tip of the \"master\". This is not strictly necessary, but\n it makes it easier to keep your history simple.\n\n * Whenever you need to test or publish your changes to topic\n branches, merge them into \"next\" branch.\n\nThe script, being an example, hardcodes the publish branch name\nto be \"next\", but it is trivial to make it configurable via\n$GIT_DIR/config mechanism.\n\nWith this workflow, you would want to know:\n\n(1) ... if a topic branch has ever been merged to \"next\". Young\n topic branches can have stupid mistakes you would rather\n clean up before publishing, and things that have not been\n merged into other branches can be easily rebased without\n affecting other people. But once it is published, you would\n not want to rewind it.\n\n(2) ... if a topic branch has been fully merged to \"master\".\n Then you can delete it. More importantly, you should not\n build on top of it -- other people may already want to\n change things related to the topic as patches against your\n \"master\", so if you need further changes, it is better to\n fork the topic (perhaps with the same name) afresh from the\n tip of \"master\".\n\nLet's look at this example:\n\n\t\t o---o---o---o---o---o---o---o---o---o \"next\"\n\t\t / / / /\n\t\t / a---a---b A / /\n\t\t/ / / /\n\t / / c---c---c---c B /\n\t / / / \\ /\n\t / / / b---b C \\ /\n\t / / / / \\ /\n ---o---o---o---o---o---o---o---o---o---o---o \"master\"\n\n\nA, B and C are topic branches.\n\n * A has one fix since it was merged up to \"next\".\n\n * B has finished. It has been fully merged up to \"master\" and \"next\",\n and is ready to be deleted.\n\n * C has not merged to \"next\" at all.\n\nWe would want to allow C to be rebased, refuse A, and encourage\nB to be deleted.\n\nTo compute (1):\n\n\tgit rev-list ^master ^topic next\n\tgit rev-list ^master next\n\n\tif these match, topic has not merged in next at all.\n\nTo compute (2):\n\n\tgit rev-list master..topic\n\n\tif this is empty, it is fully merged to \"master\".\n\nDOC_END\n",[],[469,772,802],"f77900ce-5d88-11f1-b3b4-1607ee4eb77e","pre-push.sample","019e8205-0428-7440-918e-1277cfebf8e2",["D",1780297827276],"#!/bin/sh\n\n# An example hook script to verify what is about to be pushed. Called by \"git\n# push\" after it has checked the remote status, but before anything has been\n# pushed. If this script exits with a non-zero status nothing will be pushed.\n#\n# This hook is called with the following parameters:\n#\n# $1 -- Name of the remote to which the push is being done\n# $2 -- URL to which the push is being done\n#\n# If pushing without using a named remote those arguments will be equal.\n#\n# Information about the commits which are being pushed is supplied as lines to\n# the standard input in the form:\n#\n# \n#\n# This sample shows how to prevent push of commits where the log message starts\n# with \"WIP\" (work in progress).\n\nremote=\"$1\"\nurl=\"$2\"\n\nzero=$(git hash-object --stdin &2 \"Found WIP commit in $local_ref, not pushing\"\n\t\t\texit 1\n\t\tfi\n\tfi\ndone\n\nexit 0\n",[],[469,772,809],"f778fc8c-5d88-11f1-b3b4-1607ee4eb77e","pre-merge-commit.sample","019e8205-0428-7440-918e-0ed082c5df45",["D",1780297827276],"#!/bin/sh\n#\n# An example hook script to verify what is about to be committed.\n# Called by \"git merge\" with no arguments. The hook should\n# exit with non-zero status after issuing an appropriate message to\n# stderr if it wants to stop the merge commit.\n#\n# To enable this hook, rename this file to \"pre-merge-commit\".\n\n. git-sh-setup\ntest -x \"$GIT_DIR/hooks/pre-commit\" &&\n exec \"$GIT_DIR/hooks/pre-commit\"\n:\n",[],[469,772,816],"f778ed14-5d88-11f1-b3b4-1607ee4eb77e","pre-commit.sample","019e8205-0428-7440-918e-0b39174d207b",["D",1780297827276],"#!/bin/sh\n#\n# An example hook script to verify what is about to be committed.\n# Called by \"git commit\" with no arguments. The hook should\n# exit with non-zero status after issuing an appropriate message if\n# it wants to stop the commit.\n#\n# To enable this hook, rename this file to \"pre-commit\".\n\nif git rev-parse --verify HEAD >/dev/null 2>&1\nthen\n\tagainst=HEAD\nelse\n\t# Initial commit: diff against an empty tree object\n\tagainst=$(git hash-object -t tree /dev/null)\nfi\n\n# If you want to allow non-ASCII filenames set this variable to true.\nallownonascii=$(git config --type=bool hooks.allownonascii)\n\n# Redirect output to stderr.\nexec 1>&2\n\n# Cross platform projects tend to avoid non-ASCII filenames; prevent\n# them from being added to the repository. We exploit the fact that the\n# printable range starts at the space character and ends with tilde.\nif [ \"$allownonascii\" != \"true\" ] &&\n\t# Note that the use of brackets around a tr range is ok here, (it's\n\t# even required, for portability to Solaris 10's /usr/bin/tr), since\n\t# the square bracket bytes happen to fall in the designated range.\n\ttest $(git diff-index --cached --name-only --diff-filter=A -z $against |\n\t LC_ALL=C tr -d '[ -~]\\0' | wc -c) != 0\nthen\n\tcat <<\\EOF\nError: Attempt to add a non-ASCII file name.\n\nThis can cause problems if you want to work with people on other platforms.\n\nTo be portable it is advisable to rename the file.\n\nIf you know what you are doing you can disable this check using:\n\n git config hooks.allownonascii true\nEOF\n\texit 1\nfi\n\n# If there are whitespace errors, print the offending file names and fail.\nexec git diff-index --check --cached $against --\n",[],[469,772,823],"f778e90e-5d88-11f1-b3b4-1607ee4eb77e","pre-applypatch.sample","019e8205-0428-7440-918e-04f72119843f",["D",1780297827276],"#!/bin/sh\n#\n# An example hook script to verify what is about to be committed\n# by applypatch from an e-mail message.\n#\n# The hook should exit with non-zero status after issuing an\n# appropriate message if it wants to stop the commit.\n#\n# To enable this hook, rename this file to \"pre-applypatch\".\n\n. git-sh-setup\nprecommit=\"$(git rev-parse --git-path hooks/pre-commit)\"\ntest -x \"$precommit\" && exec \"$precommit\" ${1+\"$@\"}\n:\n",[],[469,772,830],"f778e634-5d88-11f1-b3b4-1607ee4eb77e","post-update.sample","019e8205-0428-7440-918e-034061ea6f76",["D",1780297827276],"#!/bin/sh\n#\n# An example hook script to prepare a packed repository for use over\n# dumb transports.\n#\n# To enable this hook, rename this file to \"post-update\".\n\nexec git update-server-info\n",[],[469,772,837],"f778c190-5d88-11f1-b3b4-1607ee4eb77e","fsmonitor-watchman.sample","019e8205-0428-7440-918d-ffd90805a9cf",["D",1780297827276],"#!/usr/bin/perl\n\nuse strict;\nuse warnings;\nuse IPC::Open2;\n\n# An example hook script to integrate Watchman\n# (https://facebook.github.io/watchman/) with git to speed up detecting\n# new and modified files.\n#\n# The hook is passed a version (currently 2) and last update token\n# formatted as a string and outputs to stdout a new update token and\n# all files that have been modified since the update token. Paths must\n# be relative to the root of the working tree and separated by a single NUL.\n#\n# To enable this hook, rename this file to \"query-watchman\" and set\n# 'git config core.fsmonitor .git/hooks/query-watchman'\n#\nmy ($version, $last_update_token) = @ARGV;\n\n# Uncomment for debugging\n# print STDERR \"$0 $version $last_update_token\\n\";\n\n# Check the hook interface version\nif ($version ne 2) {\n\tdie \"Unsupported query-fsmonitor hook version '$version'.\\n\" .\n\t \"Falling back to scanning...\\n\";\n}\n\nmy $git_work_tree = get_working_dir();\n\nmy $retry = 1;\n\nmy $json_pkg;\neval {\n\trequire JSON::XS;\n\t$json_pkg = \"JSON::XS\";\n\t1;\n} or do {\n\trequire JSON::PP;\n\t$json_pkg = \"JSON::PP\";\n};\n\nlaunch_watchman();\n\nsub launch_watchman {\n\tmy $o = watchman_query();\n\tif (is_work_tree_watched($o)) {\n\t\toutput_result($o->{clock}, @{$o->{files}});\n\t}\n}\n\nsub output_result {\n\tmy ($clockid, @files) = @_;\n\n\t# Uncomment for debugging watchman output\n\t# open (my $fh, \">\", \".git/watchman-output.out\");\n\t# binmode $fh, \":utf8\";\n\t# print $fh \"$clockid\\n@files\\n\";\n\t# close $fh;\n\n\tbinmode STDOUT, \":utf8\";\n\tprint $clockid;\n\tprint \"\\0\";\n\tlocal $, = \"\\0\";\n\tprint @files;\n}\n\nsub watchman_clock {\n\tmy $response = qx/watchman clock \"$git_work_tree\"/;\n\tdie \"Failed to get clock id on '$git_work_tree'.\\n\" .\n\t\t\"Falling back to scanning...\\n\" if $? != 0;\n\n\treturn $json_pkg->new->utf8->decode($response);\n}\n\nsub watchman_query {\n\tmy $pid = open2(\\*CHLD_OUT, \\*CHLD_IN, 'watchman -j --no-pretty')\n\tor die \"open2() failed: $!\\n\" .\n\t\"Falling back to scanning...\\n\";\n\n\t# In the query expression below we're asking for names of files that\n\t# changed since $last_update_token but not from the .git folder.\n\t#\n\t# To accomplish this, we're using the \"since\" generator to use the\n\t# recency index to select candidate nodes and \"fields\" to limit the\n\t# output to file names only. Then we're using the \"expression\" term to\n\t# further constrain the results.\n\tmy $last_update_line = \"\";\n\tif (substr($last_update_token, 0, 1) eq \"c\") {\n\t\t$last_update_token = \"\\\"$last_update_token\\\"\";\n\t\t$last_update_line = qq[\\n\"since\": $last_update_token,];\n\t}\n\tmy $query = <<\"\tEND\";\n\t\t[\"query\", \"$git_work_tree\", {$last_update_line\n\t\t\t\"fields\": [\"name\"],\n\t\t\t\"expression\": [\"not\", [\"dirname\", \".git\"]]\n\t\t}]\n\tEND\n\n\t# Uncomment for debugging the watchman query\n\t# open (my $fh, \">\", \".git/watchman-query.json\");\n\t# print $fh $query;\n\t# close $fh;\n\n\tprint CHLD_IN $query;\n\tclose CHLD_IN;\n\tmy $response = do {local $/; };\n\n\t# Uncomment for debugging the watch response\n\t# open ($fh, \">\", \".git/watchman-response.json\");\n\t# print $fh $response;\n\t# close $fh;\n\n\tdie \"Watchman: command returned no output.\\n\" .\n\t\"Falling back to scanning...\\n\" if $response eq \"\";\n\tdie \"Watchman: command returned invalid output: $response\\n\" .\n\t\"Falling back to scanning...\\n\" unless $response =~ /^\\{/;\n\n\treturn $json_pkg->new->utf8->decode($response);\n}\n\nsub is_work_tree_watched {\n\tmy ($output) = @_;\n\tmy $error = $output->{error};\n\tif ($retry > 0 and $error and $error =~ m/unable to resolve root .* directory (.*) is not watched/) {\n\t\t$retry--;\n\t\tmy $response = qx/watchman watch \"$git_work_tree\"/;\n\t\tdie \"Failed to make watchman watch '$git_work_tree'.\\n\" .\n\t\t \"Falling back to scanning...\\n\" if $? != 0;\n\t\t$output = $json_pkg->new->utf8->decode($response);\n\t\t$error = $output->{error};\n\t\tdie \"Watchman: $error.\\n\" .\n\t\t\"Falling back to scanning...\\n\" if $error;\n\n\t\t# Uncomment for debugging watchman output\n\t\t# open (my $fh, \">\", \".git/watchman-output.out\");\n\t\t# close $fh;\n\n\t\t# Watchman will always return all files on the first query so\n\t\t# return the fast \"everything is dirty\" flag to git and do the\n\t\t# Watchman query just to get it over with now so we won't pay\n\t\t# the cost in git to look up each individual file.\n\t\tmy $o = watchman_clock();\n\t\t$error = $output->{error};\n\n\t\tdie \"Watchman: $error.\\n\" .\n\t\t\"Falling back to scanning...\\n\" if $error;\n\n\t\toutput_result($o->{clock}, (\"/\"));\n\t\t$last_update_token = $o->{clock};\n\n\t\teval { launch_watchman() };\n\t\treturn 0;\n\t}\n\n\tdie \"Watchman: $error.\\n\" .\n\t\"Falling back to scanning...\\n\" if $error;\n\n\treturn 1;\n}\n\nsub get_working_dir {\n\tmy $working_dir;\n\tif ($^O =~ 'msys' || $^O =~ 'cygwin') {\n\t\t$working_dir = Win32::GetCwd();\n\t\t$working_dir =~ tr/\\\\/\\//;\n\t} else {\n\t\trequire Cwd;\n\t\t$working_dir = Cwd::cwd();\n\t}\n\n\treturn $working_dir;\n}\n",[],[469,772,844],"f778b97a-5d88-11f1-b3b4-1607ee4eb77e","commit-msg.sample","019e8205-0428-7440-918d-fb0fed9a88a4",["D",1780297827276],"#!/bin/sh\n#\n# An example hook script to check the commit log message.\n# Called by \"git commit\" with one argument, the name of the file\n# that has the commit message. The hook should exit with non-zero\n# status after issuing an appropriate message if it wants to stop the\n# commit. The hook is allowed to edit the commit message file.\n#\n# To enable this hook, rename this file to \"commit-msg\".\n\n# Uncomment the below to add a Signed-off-by line to the message.\n# Doing this in a hook is a bad idea in general, but the prepare-commit-msg\n# hook is more suited to it.\n#\n# SOB=$(git var GIT_AUTHOR_IDENT | sed -n 's/^\$.*>\$.*$/Signed-off-by: \\1/p')\n# grep -qs \"^$SOB\" \"$1\" || echo \"$SOB\" >> \"$1\"\n\n# This example catches duplicate Signed-off-by lines.\n\ntest \"\" = \"$(grep '^Signed-off-by: ' \"$1\" |\n\t sort | uniq -c | sed -e '/^[ \t]*1[ \t]/d')\" || {\n\techo >&2 Duplicate Signed-off-by lines.\n\texit 1\n}\n",[],[469,772,851],"f778b510-5d88-11f1-b3b4-1607ee4eb77e","applypatch-msg.sample","019e8205-0428-7440-918d-f62d47729035",["D",1780297827276],"#!/bin/sh\n#\n# An example hook script to check the commit log message taken by\n# applypatch from an e-mail message.\n#\n# The hook should exit with non-zero status after issuing an\n# appropriate message if it wants to stop the commit. The hook is\n# allowed to edit the commit message file.\n#\n# To enable this hook, rename this file to \"applypatch-msg\".\n\n. git-sh-setup\ncommitmsg=\"$(git rev-parse --git-path hooks/commit-msg)\"\ntest -x \"$commitmsg\" && exec \"$commitmsg\" ${1+\"$@\"}\n:\n",[],[469,772,858],"f7ce9746-5d88-11f1-b3b4-1607ee4eb77e",["D",1780297827276],[213,214,215,216,217,218,219,220,221,222,223,224,225,226],[469,772],"f778b3da-5d88-11f1-b3b4-1607ee4eb77e","co.gitup.mac","019e8205-0428-7440-918d-f0a70827e8fc",["D",1780297827276],[],[469,869],"f7cf0546-5d88-11f1-b3b4-1607ee4eb77e",["D",1780297827276],[211,212,227,229,234,269,273,274,275,276],[469],"f7789f12-5d88-11f1-b3b4-1607ee4eb77e","settings.local.json","019e8205-0428-7440-918d-e97f6701f433","019e8205-0428-7440-918d-ee4726975efe",["D",1780297827276],"{\n \"permissions\": {\n \"allow\": [\n \"Bash(npm run dev:*)\",\n \"Bash(/Users/chris/fnifs/Projektwoche/backend/index_clean.ts)\"\n ],\n \"deny\": [],\n \"ask\": []\n }\n}\n",[],[886,879],".claude","f778b240-5d88-11f1-b3b4-1607ee4eb77e",["D",1780297827276],[209],[886],["D",1780297827276],["D",1789519842404],{"_11":12,"_154":77},{"_11":12,"_150":-5,"_76":77,"_31":75,"_151":152,"_153":30},{"_42":140,"_13":16,"_36":39,"_141":105,"_142":66,"_143":67,"_144":109,"_145":146,"_147":45,"_148":14,"_149":12},"ctx",{"_55":-5,"_175":929,"_930":931,"_932":933,"_934":30,"_935":30,"_936":30,"_937":24,"_938":-5,"_939":-7,"_940":-7,"_941":26,"_942":30,"_943":30,"_944":-5,"_945":30,"_946":30,"_947":30,"_948":-5},"ENV",{"_900":901,"_902":903,"_904":16,"_905":906,"_907":908,"_909":910,"_911":912,"_913":914,"_915":916,"_917":918,"_919":920,"_921":922,"_923":924,"_925":926,"_927":928},"REACT_APP_SENTRY_DSN","https://586020d86f05489db63a554690acf1e9@o1398359.ingest.sentry.io/6724499","RENDER_GIT_COMMIT","e87eb04e707cf64e7e532c8e8ec395f209e17f15","RENDER_GIT_BRANCH","POSTHOG_API_TOKEN","phc_nmoyuAkStEZuUp69rYlg1DZgrIt19Gx0Y4Hwf8tGgJP","POSTHOG_API_HOST","https://wart.val.town","WEB_API_TEMPLATE","https://{val}.web.val.run","APP_URL","https://www.val.town","MODULE_URL","https://esm.town","VANITY_WEB_API_TEMPLATE","https://{label}.val.run/","DENOLS_URL","https://lsp.val.town","NODE_ENV","production","CLOUDFLARE_TURNSTILE_SITE_KEY","0x4AAAAAACtaIZJH7s9rBMZ6","GOOGLE_CLIENT_ID","875989696899-jtsqkhlbdv5jrlsk8631p7ipjg3c6o62.apps.googleusercontent.com","STRIPE_PUBLISHABLE_KEY","pk_live_51N2zvWEpZTTLipIkVEwXrUG9AT0yeOOEYxszarZT1jpsZV58Ly6wlg3SltZpHN26CUalOBmUSY7adQRQiSkCZz2500qSXNkf8Y","API_URL","https://api.val.town",[],"preferencesKeybindings","default","preferencesTheme","light","preferencesFixers","preferencesCopilot","preferencesSelectionAi","preferencesCloseBrackets","preferencesChatPanelState","preferencesDprint","preferencesDenofmt","notificationCount","flagDenols","isBusinessOrgMember","businessOrgHandle","isBusinessOrgAdmin","isHigherTownieTier","navCollapsed","currentOrgId"]

Projektauswahl

Elternteil

Projektidee

Altersgruppen

Rahmen & Material

Verfügbarkeit

Danke, dein Vorschlag ist eingegangen.

Bisher eingereichte Vorschläge

Admin-Bereich - Projektauswahl

Antworten der Kinder

Projektzuteilung

Zuteilungen ansehen

Projektvorschläge von Eltern

Zeitslots

Neuen Zeitslot anlegen

Projekte

Neues Projekt anlegen

Projekt zu Zeitslot hinzufügen

Antworten der Kinder

Projektzuteilung

Zuteilung berechnen

Zuteilungsstatistik

Zuteilungen nach Kind - alle Zeitslots

Zuteilungen nach Projekt

History · backend