tsieprawski/forgejo-actions
Watch
1
0
Fork
You've already forked forgejo-actions
 0
Code Issues 4 Pull requests Projects Releases Packages Wiki Activity Actions

research: identify reusable Forgejo workflows across local repos #1

New issue
Closed
opened 2026-07-10 06:27:06 +00:00 by tsieprawski · 2 comments
tsieprawski commented 2026-07-10 06:27:06 +00:00
Owner
Copy link

Investigate how to populate this repository with reusable Forgejo workflows.

Scope:

  • revisit all repositories under ~/repo whose origin points to code.sieprawski.pl
  • inspect their existing Forgejo workflow files
  • identify workflow logic that can be extracted into reusable workflows in this repo

Initial ideas to evaluate:

  • in-house git clone and checkout helpers
  • OS dependency installation helpers for pt-get and pk add
  • Docker image build, test, and possibly publish workflows

Deliverables:

  • inventory of matching repositories
  • summary of current workflow duplication patterns
  • proposed reusable workflow set for this repository
  • notes on required inputs, secrets, and limitations for each reusable workflow
Investigate how to populate this repository with reusable Forgejo workflows. Scope: - revisit all repositories under ~/repo whose origin points to code.sieprawski.pl - inspect their existing Forgejo workflow files - identify workflow logic that can be extracted into reusable workflows in this repo Initial ideas to evaluate: - in-house git clone and checkout helpers - OS dependency installation helpers for pt-get and pk add - Docker image build, test, and possibly publish workflows Deliverables: - inventory of matching repositories - summary of current workflow duplication patterns - proposed reusable workflow set for this repository - notes on required inputs, secrets, and limitations for each reusable workflow
tsieprawski commented 2026-07-10 07:14:32 +00:00
Author
Owner
Copy link

Research summary:

Surveyed local repos under C:\Users\tomas\repos whose origin points to code.sieprawski.pl.

Canonical repos with root .forgejo/workflows found:

  • backup-orchestrator
  • docker-services
  • enslavethemstars.pl-htdocs
  • enslavethemstars.pl-rider
  • ets-services
  • rpp-lint
  • services-gator
  • services-vps
  • services-zotac
  • tone-agent-skill

Main duplication clusters:

  1. Authenticated in-house checkout via inline git clone, git fetch, git checkout, optional submodules.
    Examples:
    • backup-orchestrator/.forgejo/workflows/check.yaml
    • ets-services/.forgejo/workflows/test-integration-openwebui.yaml
    • docker-services/.forgejo/workflows/build.yaml
  2. OS package bootstrap via repeated pk add and pt-get install blocks.
    Examples:
    • backup-orchestrator/.forgejo/workflows/check.yaml
    • ets-services/.forgejo/workflows/test-integration-openwebui.yaml
  3. Docker build/test/publish flow.
    Examples:
    • docker-services/.forgejo/workflows/build.yaml
    • docker-services/.forgejo/workflows/publish-on-demand.yaml
  4. PR validation for this repo should be end-to-end against a child Forgejo plus fixture repos.
    Reference pattern:
    • services-gator/vendor/setup-forgejo/.forgejo/workflows/integration-action.yml

Created follow-up issues:

  • #2 feat: add reusable authenticated checkout workflow
  • #3 feat: add reusable Alpine and Debian package setup actions
  • #4 feat: add reusable docker build, test, and publish workflows
  • #5 feat: add PR validation workflow using child Forgejo and fixture repos

Recommended implementation order:

  1. #2 checkout
  2. #3 package setup
  3. #5 PR validation harness
  4. #4 docker build/test/publish

Note: the checkout and package setup pieces will likely be prerequisites for the fixture repos used by #5.

Research summary: Surveyed local repos under C:\Users\tomas\repos whose origin points to code.sieprawski.pl. Canonical repos with root .forgejo/workflows found: - backup-orchestrator - docker-services - enslavethemstars.pl-htdocs - enslavethemstars.pl-rider - ets-services - rpp-lint - services-gator - services-vps - services-zotac - tone-agent-skill Main duplication clusters: 1. Authenticated in-house checkout via inline git clone, git fetch, git checkout, optional submodules. Examples: - backup-orchestrator/.forgejo/workflows/check.yaml - ets-services/.forgejo/workflows/test-integration-openwebui.yaml - docker-services/.forgejo/workflows/build.yaml 2. OS package bootstrap via repeated pk add and pt-get install blocks. Examples: - backup-orchestrator/.forgejo/workflows/check.yaml - ets-services/.forgejo/workflows/test-integration-openwebui.yaml 3. Docker build/test/publish flow. Examples: - docker-services/.forgejo/workflows/build.yaml - docker-services/.forgejo/workflows/publish-on-demand.yaml 4. PR validation for this repo should be end-to-end against a child Forgejo plus fixture repos. Reference pattern: - services-gator/vendor/setup-forgejo/.forgejo/workflows/integration-action.yml Created follow-up issues: - #2 feat: add reusable authenticated checkout workflow - #3 feat: add reusable Alpine and Debian package setup actions - #4 feat: add reusable docker build, test, and publish workflows - #5 feat: add PR validation workflow using child Forgejo and fixture repos Recommended implementation order: 1. #2 checkout 2. #3 package setup 3. #5 PR validation harness 4. #4 docker build/test/publish Note: the checkout and package setup pieces will likely be prerequisites for the fixture repos used by #5.
tsieprawski commented 2026-07-10 07:28:19 +00:00
Author
Owner
Copy link

Research completed. Follow-up work has been split into implementation issues #2, #3, #4, and #5.

Research completed. Follow-up work has been split into implementation issues #2, #3, #4, and #5.
Sign in to join this conversation.
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
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#1
No description provided.