programmatic options for initializing a github wiki

[nwsparks]

Select Topic Area

Product Feedback

Body

currently there is no way to programmatically initialize a github wiki. the api has an option to enable it when creating a repository, but it will not create the initial page.

until that initial page is created the wiki cannot be cloned nor can it be pushed to. there is also no api support for the wiki.

we have a use case where we need to enable the wiki across quite a few repositories so that some additional tooling can leverage it. given the above there is no way to do this outside of manually clicking on every repository.

possible solutions:

• the create repository api could be updated to support initializing the wiki
• add api support for the wiki

related discussions:

https://github.com/orgs/community/discussions/175621
https://github.com/orgs/community/discussions/102891

[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. ⭐

[Sabari-Vasan-SM]

Hello,

Thank you for raising this issue. We are currently facing the exact same roadblock, and I want to strongly endorse the need for a programmatic solution here.

The inability to programmatically initialize a GitHub Wiki creates a significant manual overhead that defeats the purpose of automation when managing many repositories.
I believe the most efficient solution would be to update the Repository Creation/Update API to optionally accept a key (e.g., initialize_wiki: true) that automatically performs the "Create the first page" action, including creating the default Home.md page.

This would align the Wiki feature with other repository features that are fully API-controllable (like Issues, Projects, etc.).

It would require minimal changes to the existing API structure.

🛠️ Use Case: Automated Tooling Setup
Our specific use case involves a compliance and documentation pipeline:

We require every new repository to have a standardized set of documentation (e.g., README.md, CONTRIBUTING.md, and a Standard Operating Procedure (SOP) Wiki).

Goal: Use a custom tool to clone the Wiki (Git repo) and push a set of pre-filled, templated SOP pages.

Current Blocker: The tool fails on the git clone step until the Wiki is manually initialized, making the entire SOP documentation process a manual chore.

[sgoldson]

This is an issue in my use case as well. Strange you can migrate all pieces of a wiki, but you cannot enable it with automation.

[electrocucaracha]

Same here — I ran into the exact same roadblock. I even tried using Selenium to automate the Wiki initialization, but it’s far from practical: the browser requires an active session, the workflow is fragile, and any UI change can break the automation.

For context, here’s the approach I tried:

• Launch a real browser via Selenium.
• Navigate to /<org>/<repo>/wiki.
• Click “Create the first page.”
• Add a title + Markdown content.
• Submit the form.