msz/pool-to-catalog
1
0
Fork 0
Code Pull requests 1 Packages Activity Actions

Prepare the forgejo action for deployment #1

Open
msz wants to merge 1 commit from action into main
pull from: action
merge into: msz:main
Conversation 0 Commits 1 Files changed 1 +11 -13
msz commented 2025-11-14 19:36:07 +00:00
Owner
Copy link

This makes the forgejo action more similar to the emerging standard in the lab. The runs_on value should be enough to have it picked up by the runner, as long as the repo lives in a privileged org.

Although we do not have annexed content, the checkout action is switched to datalad-clone-action following mih's suggestion to eat more of our dog food.

What's missing is a schedule specification, and possibly a qualifier constraing it to running in specific orgs / repos.

The paths to place the catalog in are my best guess, so at this stage this needs feedback from @mih

This makes the forgejo action more similar to the emerging standard in the lab. The `runs_on` value should be enough to have it picked up by the runner, as long as the repo lives in a privileged org. Although we do not have annexed content, the checkout action is switched to datalad-clone-action following mih's suggestion to eat more of our dog food. What's missing is a schedule specification, and possibly a qualifier constraing it to running in specific orgs / repos. The paths to place the catalog in are my best guess, so at this stage this needs feedback from @mih
This makes the forgejo action more similar to the emerging standard in
the lab. The runs_on value should be enough to have it picked up by the
runner, as long as the repo lives in a priviledged org.

Although we do not have annexed content, the checkout action is switched
to datalad-clone-action following mih's suggestion to eat more of our
dog food.

What's missing is a schedule specification, and possibly a qualifier
constraing it to running in specific orgs / repos (but the deployment
repo is TBD).
msz changed title from Prepare the forgejo action for deployment to WIP: Prepare the forgejo action for deployment 2025-11-14 19:36:25 +00:00
msz changed title from WIP: Prepare the forgejo action for deployment to Prepare the forgejo action for deployment 2025-11-14 19:36:28 +00:00
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin action:action
git switch action

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff action
git switch action
git rebase main
git switch main
git merge --ff-only action
git switch action
git rebase main
git switch main
git merge --no-ff action
git switch main
git merge --squash action
git switch main
git merge --ff-only action
git switch main
git merge action
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
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
msz/pool-to-catalog!1
No description provided.