chore: scaffold repo baseline, licensing, and quality gates #6

Closed
opened 2026-07-10 07:28:34 +00:00 by tsieprawski · 0 comments
Owner

Set up this repository so it is green and baseline-tested before reusable workflow implementation lands.

Requirements:

  • add proper README content for the repo purpose and intended structure
  • set up
    euse
  • all files must be explicitly tagged; do not rely on magic file wildcards
  • license is proprietary
  • copyright holder: Tomasz Sieprawski tomasz@sieprawski.pl
  • copyright year: 2026

Quality and validation scope:

  • research and add an appropriate workflow linter for Forgejo workflow files
  • prefer reusing an existing image from docker-services if one already fits
  • otherwise do not invent a new image yet; use a minimal lpine:latest base, not edge, and install only what is necessary with pk add
  • make the repo green with baseline checks even before reusable workflow implementation issues land
  • once implementation lands later, quality gates should already be in place and enforceable

Expected outcomes:

  • repo has baseline docs and licensing hygiene
  • repo has explicit file-level SPDX tagging
  • repo has at least one CI path that validates the baseline state
  • repo is in a good state to make the future PR validation workflow a required check
Set up this repository so it is green and baseline-tested before reusable workflow implementation lands. Requirements: - add proper README content for the repo purpose and intended structure - set up euse - all files must be explicitly tagged; do not rely on magic file wildcards - license is proprietary - copyright holder: Tomasz Sieprawski <tomasz@sieprawski.pl> - copyright year: 2026 Quality and validation scope: - research and add an appropriate workflow linter for Forgejo workflow files - prefer reusing an existing image from docker-services if one already fits - otherwise do not invent a new image yet; use a minimal lpine:latest base, not edge, and install only what is necessary with pk add - make the repo green with baseline checks even before reusable workflow implementation issues land - once implementation lands later, quality gates should already be in place and enforceable Expected outcomes: - repo has baseline docs and licensing hygiene - repo has explicit file-level SPDX tagging - repo has at least one CI path that validates the baseline state - repo is in a good state to make the future PR validation workflow a required check
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
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
tsieprawski/forgejo-actions#6
No description provided.