forgejo-contrib-forgejo-cli-issues-228.md
Watch20
Star402
Fork
You've already forked forgejo-cli
CodeIssues 44Pull requests 8Releases 11Packages 2WikiActivity
Closed
opened 2025-10-19 20:13:57 +02:00 by Cyborus · 2 comments
Cyborus commented 2025-10-19 20:13:57 +02:00
Member
Copy link
Since Forgejo+Woodpecker is such a common combination — Codeberg uses that combo, I use that combo for my personal forge — it would be nice to support Woodpecker for fj actions commands in addition to Forgejo Actions. Renaming actions to ci (but keeping actions as an alias) would be good since that would be more general
I'm not sure exactly how to detect the Woodpecker instance from a repo. It could be pulled from commit statuses, but that wouldn't work well for repo-level commands which all the actions commands are. It could be pulled from the webhook, but that isn't publicly accessible
Since Forgejo+Woodpecker is such a common combination — Codeberg uses that combo, I use that combo for my personal forge — it would be nice to support Woodpecker for fj actions commands in addition to Forgejo Actions. Renaming actions to ci (but keeping actions as an alias) would be good since that would be more general I'm not sure exactly how to detect the Woodpecker instance from a repo. It could be pulled from commit statuses, but that wouldn't work well for repo-level commands which all the actions commands are. It could be pulled from the webhook, but that isn't publicly accessible
Cyborus added the Kind/Feature label 2025-10-19 20:13:57 +02:00
Cyborus referenced this issue from forgejo/forgejo 2025-10-21 23:39:20 +02:00 feat(ui): custom external units for repository #8396
Cyborus added the [ Status
Blocked ](/forgejo-contrib/forgejo-cli/issues?labels=173010) label 2025-12-01 17:05:50 +01:00
pat-s commented 2025-12-30 23:32:31 +01:00
Contributor
Copy link
I don't think this is needed (nor a good idea) since there is a dedicated CLI for Woodpecker (and forks). In the end you would only replicate the existing WP CLI commands to interact with the WP API. Additionally, you would likely need to support multiple (major) versions as not all instances are always on the last version.
All in all I'd argue that this is an off-topic use case for the Forgejo CLI and it would be better to stick with the "do one thing and do that well" philosophy.
I don't think this is needed (nor a good idea) since there is a dedicated CLI for Woodpecker (and forks). In the end you would only replicate the existing WP CLI commands to interact with the WP API. Additionally, you would likely need to support multiple (major) versions as not all instances are always on the last version. All in all I'd argue that this is an off-topic use case for the Forgejo CLI and it would be better to stick with the "do one thing and do that well" philosophy.
👍 1
Cyborus commented 2026-01-11 17:03:13 +01:00
Author
Member
Copy link
I find this convincing, thank you for the input!
I find this convincing, thank you for the input!
Cyborus closed this issue 2026-01-11 17:03:13 +01:00
Sign in to join this conversation.
No Branch/Tag specified
main
renovate/lock-file-maintenance
renovate/serde-saphyr-0.x
docs/contributing
no-port-in-refspec
login/v16.next.forgejo.org
crates-io-publish
0.5.x
compile-time-fluent
0.4.x
localization-alias-demo
api_url_field
v0.5.0
v0.4.1
v0.4.0
v0.3.0
v0.2.0
v0.1.1
v0.1.0
v0.0.4
v0.0.3
v0.0.2
v0.0.1
Labels
Clear labels[ Kind/Breaking Breaking change that won't be backward compatible
](#)[ Kind/Bug Something is not working
](#)[ Kind/Design Discussion about UI/UX design
](#)[ Kind/Documentation Documentation changes
](#)[ Kind/Enhancement Improve existing functionality
](#)[ Kind/Feature New functionality
](#)[ Kind/Security This is security issue
](#)[ Kind/Testing Issue or pull request related to testing
](#)[ Kind/Upstream This is an issue with upstream software (Forgejo) that is probably not our fault
](#)
[ Priority
Critical The priority is critical
](#)[ Priority
High The priority is high
](#)[ Priority
Low The priority is low
](#)[ Priority
Medium The priority is medium
](#)
[ Reviewed
Confirmed Issue has been confirmed
](#)[ Reviewed
Duplicate This issue or pull request already exists
](#)[ Reviewed
Invalid Invalid issue
](#)[ Reviewed
Won't Fix This issue won't be fixed
](#)
[ Status
Abandoned Somebody has started to work on this but abandoned work
](#)[ Status
Blocked Something is blocking this issue or pull request
](#)[ Status
Need More Info Feedback is required to reproduce issue or to continue work
](#)
[ Suspicious
](#)
No labels Kind/Breaking Kind/Bug Kind/Design Kind/Documentation Kind/Enhancement Kind/Feature Kind/Security Kind/Testing Kind/Upstream [ Priority
Critical ](/forgejo-contrib/forgejo-cli/issues?labels=173012) [ Priority
High ](/forgejo-contrib/forgejo-cli/issues?labels=173013) [ Priority
Low ](/forgejo-contrib/forgejo-cli/issues?labels=173015) [ Priority
Medium ](/forgejo-contrib/forgejo-cli/issues?labels=173014) [ Reviewed
Confirmed ](/forgejo-contrib/forgejo-cli/issues?labels=173007) [ Reviewed
Duplicate ](/forgejo-contrib/forgejo-cli/issues?labels=173005) [ Reviewed
Invalid ](/forgejo-contrib/forgejo-cli/issues?labels=173006) [ Reviewed
Won't Fix ](/forgejo-contrib/forgejo-cli/issues?labels=173008) [ Status
Abandoned ](/forgejo-contrib/forgejo-cli/issues?labels=173011) [ Status
Blocked ](/forgejo-contrib/forgejo-cli/issues?labels=173010) [ Status
Need More Info ](/forgejo-contrib/forgejo-cli/issues?labels=173009) Suspicious
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
Notifications Subscribe
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
forgejo-contrib/forgejo-cli#228
WritePreview
Loading…
Add table
| Rows | | | Columns | |
CancelOK
Add a link
Url Description Hint: With a URL in your clipboard, you can paste directly into the editor to create a link.
CancelOK
CancelSave
Reference in a new issue
Repository
forgejo-contrib/forgejo-cli
Title
Body
Create issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
No Yes