Request for programmatic initialization of repository wikis

[YCAD-pro]

Select Topic Area

Question

Body

Hey GitHub team,

I’d love to see some improvements in how wikis are initialized for repositories. Right now, even if we set has_wiki to true when creating a repo, the wiki repo doesn’t actually exist until someone manually creates the first page through the web interface. This makes automation tricky for CI/CD setups and other programmatic workflows.

It would be awesome if we could have one (or all) of these solutions:
1. Auto-create the wiki repo when has_wiki: true is set—if we enable it, it’s because we plan to use it.
2. Expose an API endpoint to create the first wiki page programmatically.
3. Allow pushing to initialize the wiki, so that a git push to the .wiki.git repo triggers its creation instead of failing.

Any of these would make managing wikis way smoother for automated workflows. Hope this gets considered—thanks for all the great work!

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

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[YCAD-pro]

This development look interesting if we are agree about the utility of wikis.

[gregnrobinson]

Can we please allow for the {repo_name}.wiki.git repository to be cloneable if the wiki setting is enabled on the repo. We are trying to integrate and populate the wiki pages dynamically with information when repositories are created, but when we have to manually create the first page in the UI, it doesn't allow this automation to work.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[electrocucaracha]

This topic has not been addressed properly