ldraney/daily-100
Archived
1
0
Fork 0
Code Issues 13 Pull requests Projects Releases Packages Wiki Activity Actions

Infra: Forgejo repos (daily-100, daily-100-api) #10

New issue
Open
opened 2026-03-28 02:10:27 +00:00 by forgejo_admin · 0 comments
forgejo_admin commented 2026-03-28 02:10:27 +00:00
Copy link

Type

Infra

Lineage

Standalone — scoped from Daily 100 design spec.

Repo

forgejo_admin/daily-100

User Story

As a developer
I want organized Forgejo repositories with CI
So that code changes are validated automatically

Context

Two repos already created: daily-100 (SvelteKit frontend + HTML prototype) and daily-100-api (FastAPI backend). This ticket tracks branch protection setup and Woodpecker CI pipeline configuration for both repos.

File Targets

Files the agent should modify or create:

  • .woodpecker.yml -- CI pipeline for daily-100
  • README.md -- project description and setup instructions

Files the agent should NOT touch:

  • Source code files -- separate tickets

Acceptance Criteria

  • Branch protection enabled on main branch
  • Woodpecker CI pipeline configured
  • README updated with project description
  • Push to branch triggers CI pipeline

Test Expectations

  • CI pipeline triggers on push
  • Pipeline runs lint and build steps
  • Run command: push to feature branch and verify CI

Constraints

  • Use Woodpecker CI (platform standard)
  • Match existing pal-e platform CI patterns

Checklist

  • PR opened
  • Tests pass
  • No unrelated changes

Related

  • daily-100 -- project
### Type Infra ### Lineage Standalone — scoped from Daily 100 design spec. ### Repo `forgejo_admin/daily-100` ### User Story As a developer I want organized Forgejo repositories with CI So that code changes are validated automatically ### Context Two repos already created: `daily-100` (SvelteKit frontend + HTML prototype) and `daily-100-api` (FastAPI backend). This ticket tracks branch protection setup and Woodpecker CI pipeline configuration for both repos. ### File Targets Files the agent should modify or create: - `.woodpecker.yml` -- CI pipeline for daily-100 - `README.md` -- project description and setup instructions Files the agent should NOT touch: - Source code files -- separate tickets ### Acceptance Criteria - [ ] Branch protection enabled on main branch - [ ] Woodpecker CI pipeline configured - [ ] README updated with project description - [ ] Push to branch triggers CI pipeline ### Test Expectations - [ ] CI pipeline triggers on push - [ ] Pipeline runs lint and build steps - Run command: push to feature branch and verify CI ### Constraints - Use Woodpecker CI (platform standard) - Match existing pal-e platform CI patterns ### Checklist - [ ] PR opened - [ ] Tests pass - [ ] No unrelated changes ### Related - `daily-100` -- project
Commenting is not possible because the repository is archived.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ldraney/daily-100#10
No description provided.