list existing wiki repos for a user/organsation?

[pabs3]

Select Topic Area

Question

Body

Using the REST API, I can list the repos for a user/organisation, and whether or not each repo has the wiki feature enabled, but repos that have the wiki feature enabled, don't necessarily have a wiki repo created for that wiki.

So I want to be able to list all of the existing wiki repos for a user/organisation. Does anyone know if this is possible, or should I brute force it instead?

For example, https://github.com/pabs3/whowatch has the wiki feature enabled, but the https://github.com/pabs3/whowatch.wiki.git repo does not exist.

I want to be able to automatically clone all my GitHub repos locally, including the wiki repos.

[54J4N]

Hi @pabs3 , great question! GitHub does not provide a direct API to list wikis, but you can determine which repositories have the wiki feature enabled by checking the has_wiki field. Below are two methods to achieve this using the GitHub API:

curl -H "Authorization: token YOUR_GITHUB_TOKEN" \
     -H "Accept: application/vnd.github.v3+json" \
     "https://api.github.com/users/pabs3/repos?per_page=100" | jq '.[] | select(.has_wiki == true) | .name'

Alternatively, you can check if a specific repository has the wiki feature enabled using the following command:

curl -H "Authorization: token YOUR_GITHUB_TOKEN" \
     -H "Accept: application/vnd.github.v3+json" \
     "https://api.github.com/repos/pabs3/REPO_NAME"

Look for the "has_wiki": true field in the response. This confirms whether the wiki feature is enabled for a specific repository of the user pabs3.

[pabs3]

I mentioned that feature in my initial post and am already using it, but there are a lot of repos that have the wiki feature enabled but do not have any wiki repo created, so this means I waste a lot of requests on repos that don't exist.

Could you escalate this to internal feature development teams?

[54J4N]

I understand your concern. You can submit a request here:
GitHub Feedback Discussions: https://github.com/orgs/community/discussions/categories/feedback
let me know! .

[pabs3]

@54J4N I tried creating a new discussion there, but got an error unfortunately:

 Sorry, we didn't recognize that category! Please choose one of the following valid categories.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐