GENERAL/ninja-library
Watch
6
0
Fork
You've already forked ninja-library
 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Store the package as a downloadable artifact in the Packages feature of Forgejo #1

New issue
Closed
opened 2026-09-04 09:36:12 +00:00 by shuber · 4 comments
shuber commented 2026-09-04 09:36:12 +00:00
Owner
Copy link
No description provided.
shuber commented 2026-09-04 09:36:35 +00:00
Author
Owner
Copy link

@opencode see the title. Implement as much as possible, and let me know what I have to do if you cannot do it on your own.

@opencode see the title. Implement as much as possible, and let me know what I have to do if you cannot do it on your own.
shuber commented 2026-09-04 11:07:33 +00:00
Author
Owner
Copy link

@opencode see the title. Implement as much as possible, and let me know what I have to do if you cannot do it on your own.

@opencode see the title. Implement as much as possible, and let me know what I have to do if you cannot do it on your own.
forgejo-actions commented 2026-09-04 11:10:23 +00:00
Copy link

I have implemented a Forgejo Action workflow to automate the publication of the ninja-api package to the Forgejo PyPI registry.

The new workflow is located at .forgejo/workflows/publish-package.yaml. It builds the package (sdist and wheel) and uses twine to upload it whenever a tag matching v* is pushed.

To enable this, you must:

  1. Add a Secret: Create a secret named FORGEJO_TOKEN in the repository settings with permissions to upload packages.
  2. Publish a Version: Create and push a tag (e.g., git tag v1.0.0 && git push origin v1.0.0) to trigger the publication.
I have implemented a Forgejo Action workflow to automate the publication of the `ninja-api` package to the Forgejo PyPI registry. The new workflow is located at `.forgejo/workflows/publish-package.yaml`. It builds the package (sdist and wheel) and uses `twine` to upload it whenever a tag matching `v*` is pushed. **To enable this, you must:** 1. **Add a Secret**: Create a secret named `FORGEJO_TOKEN` in the repository settings with permissions to upload packages. 2. **Publish a Version**: Create and push a tag (e.g., `git tag v1.0.0 && git push origin v1.0.0`) to trigger the publication.
forgejo-actions commented 2026-09-04 11:10:25 +00:00
Copy link

Created branch opencode-1788520068.367248 with changes via Action Run.
Create a PR from this branch
Note: Passing a pr-creation-pat with read/write repository access as input allows creating these PRs automagically

Created branch [opencode-1788520068.367248](https://git.datajob.de/GENERAL/ninja-library/src/branch/opencode-1788520068.367248) with changes via [Action Run](https://git.datajob.de/GENERAL/ninja-library/actions/runs/1). [Create a PR from this branch](https://git.datajob.de/GENERAL/ninja-library/compare/main...opencode-1788520068.367248) <sub>Note: Passing a pr-creation-pat with read/write repository access as input allows creating these PRs automagically</sub>
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
ci-publish-workflow
opencode-1788520068.367248
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
2 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
GENERAL/ninja-library#1
No description provided.