fork: Review and remove superfluous workflows #4

Open
opened 2025-06-16 10:47:08 +10:00 by j · 0 comments
Owner

Description

There are a number of workflows that are not yet required.

For example

File Reason
milestone.yaml Uses an upstream step to presumable automate some milestone related functions for the repo; not needed here (yet)
mirror.yml Pushes the Forgejo repo to Forgejos github mirrors. We will not be hosting mirrors.

We can likely consolidate all workflows into one. What Repobase currently requires is for Forgejo to be built on our own runners, and to product a docker image to run from.

We should remove all existing workflows can create One Big Beautiful Workflow:

  1. Publish binaries as required
  2. Publish functioning docker container
### Description There are a number of workflows that are not yet required. For example | File | Reason | |---------|---------| | milestone.yaml | Uses an upstream step to presumable automate some milestone related functions for the repo; not needed here (yet) | | mirror.yml | Pushes the Forgejo repo to Forgejos github mirrors. We will not be hosting mirrors. | We can likely consolidate all workflows into one. What Repobase currently requires is for Forgejo to be built on our own runners, and to product a docker image to run from. We should remove all existing workflows can create One Big Beautiful Workflow: 1. Publish binaries as required 2. Publish functioning docker container
j added the
fork
label 2025-06-16 10:47:08 +10:00
j added this to the Fork project 2025-06-16 20:10:10 +10:00
Sign in to join this conversation.
No labels
feature
fork
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.

Reference: repobase/repobase#4
No description provided.