REST API support for “Make profile private and hide activity”

[CKMz17]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Profile

Body

GitHub provides the “Make profile private and hide activity” setting
in the web UI, but the public REST API does not expose a field or
endpoint to read or modify it.

Please add API support, for example:

PATCH /user
{
"profile_visibility": "private"
}

or document the reason why this setting is intentionally unavailable
through the API.

Use case: automating profile visibility changes from scripts

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

[iawaisahmd]

this would be useful beyond simple scripts, especially for organizations or developers managing multiple accounts/environments. if github doesn't want to expose write access for security reasons, even a read-only field in GET /user would help automation detect the current visibility state instead of relying on the web ui. a dedicated endpoint with explicit permissions would also be safer than extending general profile write access.