forge/forge
11
8
Fork 7
Code Issues 98 Pull requests Projects 2 Wiki Activity Actions

Forgejo action does not work with short name #557

New issue
Closed
opened 2026-05-06 08:53:11 +00:00 by lecris · 7 comments
lecris commented 2026-05-06 08:53:11 +00:00
Contributor
Copy link

Summary

Local forgejo action names like ci/testing-farm@main should in principle be equivalent to https://forge.fedoraproject.org/ci/testing-farm@main, but that's not the case it seems (probably due to setup).

Details

Here is an example run as ci/testing-farm@main and failing to resolve, while this one with https://forge.fedoraproject.org/ci/testing-farm@main manages to resolve

  ☁️  git fetch 'https://data.forgejo.org/actions/checkout' # ref=v6
  ☁️  git clone 'https://data.forgejo.org/ci/testing-farm' # ref=main
⚙️ [runner]: unable to clone 'https://data.forgejo.org/ci/testing-farm' to '/data/.cache/act/78/89526b02598dc0a55fc9fac540d6a226000bf241be6ecbf4bcc412cf1b9f1c': Cloning into bare repository '/data/.cache/act/78/89526b02598dc0a55fc9fac540d6a226000bf241be6ecbf4bcc412cf1b9f1c'...\nremote: Not found.\nfatal: repository 'https://data.forgejo.org/ci/testing-farm/' not found: exit status 128

(it is trying to get them from forgejo instead of forge.fedoraproject.org)

### Summary Local forgejo action names like `ci/testing-farm@main` should in principle be equivalent to `https://forge.fedoraproject.org/ci/testing-farm@main`, but that's not the case it seems (probably due to setup). ### Details [Here](https://forge.fedoraproject.org/ci/_atomic-desktops-config/actions/runs/1/jobs/0/attempt/1) is an example run as `ci/testing-farm@main` and failing to resolve, while [this one](https://forge.fedoraproject.org/ci/_atomic-desktops-config/actions/runs/2/jobs/0/attempt/1) with `https://forge.fedoraproject.org/ci/testing-farm@main` manages to resolve <details> ``` ☁️ git fetch 'https://data.forgejo.org/actions/checkout' # ref=v6 ☁️ git clone 'https://data.forgejo.org/ci/testing-farm' # ref=main ⚙️ [runner]: unable to clone 'https://data.forgejo.org/ci/testing-farm' to '/data/.cache/act/78/89526b02598dc0a55fc9fac540d6a226000bf241be6ecbf4bcc412cf1b9f1c': Cloning into bare repository '/data/.cache/act/78/89526b02598dc0a55fc9fac540d6a226000bf241be6ecbf4bcc412cf1b9f1c'...\nremote: Not found.\nfatal: repository 'https://data.forgejo.org/ci/testing-farm/' not found: exit status 128 ``` (it is trying to get them from forgejo instead of forge.fedoraproject.org) </details>
ryanlerch added this to the Backlog project 2026-05-14 05:44:31 +00:00
humaton modified the project from Backlog to Sprint 21 2026-05-18 10:29:35 +00:00
ryanlerch commented 2026-05-25 08:51:53 +00:00
Owner
Copy link

ok, except in your example, if we change DEFAULT_ACTIONS_URL away from the the default of data.forgejo.org the actions/checkout action shortname wont resolve anymore.

ok, except in your example, if we change [DEFAULT_ACTIONS_URL](https://forgejo.org/docs/latest/admin/config-cheat-sheet/#actions-actions) away from the the default of `data.forgejo.org` the `actions/checkout` action shortname wont resolve anymore.
ryanlerch commented 2026-05-25 08:55:26 +00:00
Owner
Copy link

one workaround here would be to create an org actions on forge.fp.o and mirror the standard actions on https://data.forgejo.org/actions/

then we could change DEFAULT_ACTIONS_URL to https://forge.fedoraproject.org

that org would need to be maintained by someone though, if more actions are added.

one workaround here would be to create an org `actions` on forge.fp.o and mirror the standard actions on https://data.forgejo.org/actions/ then we could change `DEFAULT_ACTIONS_URL` to https://forge.fedoraproject.org that org would need to be maintained by someone though, if more actions are added.
lecris commented 2026-05-25 09:02:17 +00:00
Author
Contributor
Copy link

I expect this is a common issue in upstream. My thinking is to allow DEFAULT_ACTIONS_URL to be a list behaving as fallback. There would be potential name collisions in both cases.

At least mirroring should not be that problematic, since that is done in upstream just as well https://code.forgejo.org/actions

I expect this is a common issue in upstream. My thinking is to allow `DEFAULT_ACTIONS_URL` to be a list behaving as fallback. There would be potential name collisions in both cases. At least mirroring should not be that problematic, since that is done in upstream just as well https://code.forgejo.org/actions
ryanlerch commented 2026-05-25 09:46:10 +00:00
Owner
Copy link

AUIU, the current setup we have would behave the same way as you are experiencing on codeberg -- ci/testing-farm@main would not resolve to codeberg.org/ci/testing-farm@main -- it would resolve to data.forgejo.org, and fail just as it does on forge.

That said, the mirroring should work -- its just who will maintain it.

The other option is to just use full URIs when referring to non-default actions (i.e.) in the actions provided by forgejo itself.

AUIU, the current setup we have would behave the same way as you are experiencing on codeberg -- ci/testing-farm@main would not resolve to codeberg.org/ci/testing-farm@main -- it would resolve to data.forgejo.org, and fail just as it does on forge. That said, the mirroring should work -- its just who will maintain it. The other option is to just use full URIs when referring to non-default actions (i.e.) in the actions provided by forgejo itself.
humaton commented 2026-05-25 11:02:04 +00:00
Owner
Copy link

I think we should do the mirror, for now I will be maintaining the org. Will create SOP's for it and eventually find more maintainers.

I think we should do the mirror, for now I will be maintaining the org. Will create SOP's for it and eventually find more maintainers.
ryanlerch commented 2026-05-26 03:43:49 +00:00
Owner
Copy link

@humaton the new org has been created, and i have mirrored all the repos on code.forgejo.org/actions to the new org:

https://forge.fedoraproject.org/actions

@humaton the new org has been created, and i have mirrored all the repos on code.forgejo.org/actions to the new org: https://forge.fedoraproject.org/actions
ryanlerch commented 2026-05-26 03:45:07 +00:00
Owner
Copy link

final step is to update the config changing DEFAULT_ACTIONS_URL to forge.fedoraproject.org and then test -- will do this later today when more people are around to tell me if it breaks any actions.

final step is to update the config changing DEFAULT_ACTIONS_URL to `forge.fedoraproject.org` and then test -- will do this later today when more people are around to tell me if it breaks any actions.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
test
docs
No results found.
Labels
Clear labels   
Backlog Status
Needs Review
 Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
 Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and could be worked on immediately when capacity is available.

  
Chore
Tasks that are necessary but don't directly deliver new value to the end-user. These are internal tasks like updating a library, managing user accounts, or setting up a new service.

  
points
01
 A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
 This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
 medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
 a significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
 complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
 Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint.

  
Priority
High
 This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
 This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
 This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Sprint Status
Blocked
 Indicates the work cannot proceed. There is a dependency or an issue that is preventing the team from completing the task. This is a flag for the Scrum Master to help unblock the team.

  
Sprint Status
Done
 Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
 This label is for work that a developer is actively working on. This is usually what you'll see on the "In Progress" column of your project board.

  
Sprint Status
Review
 This indicates that the work is complete, but it is now in a review state. This could mean a peer code review, a QA check, or a review by the Product Owner.

  
Sprint Status
To Do
 Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt
work that improves the codebase without adding new features. It's work that pays down the "debt" you've accumulated, such as refactoring a messy piece of code, improving test coverage.

  
Work Item
Bug
 Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic

  
Work Item
Spike

  
Work Item
Task

  
Work Item
User Story

No labels
Backlog Status
Needs Review
Backlog Status
Ready
Chore
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Sprint 21
Assignees
Clear assignees
No assignees
ryanlerch
3 participants
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
forge/forge#557
No description provided.