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

feat: add PR validation workflow using child Forgejo and fixture repos #5

New issue
Open
opened 2026-07-10 07:14:18 +00:00 by tsieprawski · 0 comments
tsieprawski commented 2026-07-10 07:14:18 +00:00
Owner
Copy link

Research from #1 indicates this repository should have its own required PR validation workflow, and that the best validation model is end-to-end testing against a child Forgejo instance.

Reference pattern:

  • services-gator/vendor/setup-forgejo/.forgejo/workflows/integration-action.yml
  • related setup-forgejo testdata workflows under vendor/setup-forgejo/testdata

Proposed scope:

  • create a pull_request workflow in this repo that boots a child Forgejo and runner
  • publish the workflow or action under test into that child Forgejo
  • create one or more fixture repos that call the reusable workflows from this repo
  • verify success and expected outputs through end-to-end workflow runs
  • make this PR workflow suitable as a required check

Goal:
Validate reusable workflows the same way callers will actually use them, instead of only linting YAML locally.

Research from #1 indicates this repository should have its own required PR validation workflow, and that the best validation model is end-to-end testing against a child Forgejo instance. Reference pattern: - services-gator/vendor/setup-forgejo/.forgejo/workflows/integration-action.yml - related setup-forgejo testdata workflows under vendor/setup-forgejo/testdata Proposed scope: - create a pull_request workflow in this repo that boots a child Forgejo and runner - publish the workflow or action under test into that child Forgejo - create one or more fixture repos that call the reusable workflows from this repo - verify success and expected outputs through end-to-end workflow runs - make this PR workflow suitable as a required check Goal: Validate reusable workflows the same way callers will actually use them, instead of only linting YAML locally.
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#5
No description provided.