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 reusable authenticated checkout workflow #2

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

Research from #1 shows the same manual clone/fetch/checkout flow repeated across multiple repos and workflows.

Representative examples:

  • backup-orchestrator/.forgejo/workflows/check.yaml
  • ets-services/.forgejo/workflows/test-integration-openwebui.yaml
  • enslavethemstars.pl-rider/.forgejo/workflows/build.yaml
  • enslavethemstars.pl-htdocs/.forgejo/workflows/deploy-staging.yaml
  • docker-services/.forgejo/workflows/build.yaml

Proposed scope:

  • create a reusable Forgejo workflow for authenticated checkout from the current repo
  • support checkout by SHA/ref
  • support optional submodule init
  • support configurable target directory
  • support the current in-house HTTPS credential pattern

Goal:
Remove repeated inline git clone, git fetch, and git checkout logic from caller workflows.

Research from #1 shows the same manual clone/fetch/checkout flow repeated across multiple repos and workflows. Representative examples: - backup-orchestrator/.forgejo/workflows/check.yaml - ets-services/.forgejo/workflows/test-integration-openwebui.yaml - enslavethemstars.pl-rider/.forgejo/workflows/build.yaml - enslavethemstars.pl-htdocs/.forgejo/workflows/deploy-staging.yaml - docker-services/.forgejo/workflows/build.yaml Proposed scope: - create a reusable Forgejo workflow for authenticated checkout from the current repo - support checkout by SHA/ref - support optional submodule init - support configurable target directory - support the current in-house HTTPS credential pattern Goal: Remove repeated inline git clone, git fetch, and git checkout logic from caller workflows.
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#2
No description provided.