Back to Codeberg

list ".wiki" repos too #206

forgejo-contrib-forgejo-cli-issues-206.md

latest7.5 KB
Original Source

forgejo-contrib/forgejo-cli

Watch20

Star402

Fork

You've already forked forgejo-cli

51

CodeIssues 44Pull requests 8Releases 11Packages 2WikiActivity

list ".wiki" repos too #206

New issue

Open

opened 2025-06-03 17:21:22 +02:00 by daniel-baumann · 1 comment

daniel-baumann commented 2025-06-03 17:21:22 +02:00

Contributor

Copy link

Hi,

when creating a wiki in a repo, forgejo stores it as $repo.wiki repo, e.g. /daniel/foo is the repo and the wiki attached to is /daniel/foo.wiki.

Unfortunately, fj doesn't list foo.wiki, only foo. It would be nice, if theres a way for fj to "get" there's a separate wiki repo attached to the main repo, to also list this when asking for the list of repos of a user.

Regards,
Daniel

Hi, when creating a wiki in a repo, forgejo stores it as $repo.wiki repo, e.g. /daniel/foo is the repo and the wiki attached to is /daniel/foo.wiki. Unfortunately, fj doesn't list foo.wiki, only foo. It would be nice, if theres a way for fj to "get" there's a separate wiki repo attached to the main repo, to also list this when asking for the list of repos of a user. Regards, Daniel

Cyborus commented 2025-08-03 22:08:51 +02:00

Member

Copy link

I'm planning to include this as part of the --all feature from #189.

Since pagination is handled by forgejo rather than fj, including the .wiki for the returned repos would mean the page length would be different for every page and I couldn't give an accurate total count. That's not an issue if you're requesting the entire list of repos, though. So my plan is something like a --really-all or --include-wikis flag in addition to --all.

Is that okay?

I'm planning to include this as part of the --all feature from #189. Since pagination is handled by forgejo rather than fj, including the .wiki for the returned repos would mean the page length would be different for every page and I couldn't give an accurate total count. That's not an issue if you're requesting the entire list of repos, though. So my plan is something like a --really-all or --include-wikis flag in addition to --all. Is that okay?

Sign in to join this conversation.

No Branch/Tag specified

BranchesTags

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

2 participants

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#206

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