Organization Archiving GA Feedback

[ahpook]

Select Topic Area

Product Feedback

Body

Following along on the public beta of Organization Archiving (and the excellent community feedback from the discussion here), we are taking archiving to the moon! 🚀 Well, to General Availability at any rate. We incorporated the suggestion to make the archive state more visible, for example there's now a tag in the profile page's list of your orgs:

One other addition you'll notice is that the act of archiving an organization now sends a notification email to all the owners of the organization, just as a heads-up that the state has changed.

We've tried to be more clear in the inline text and docs that archiving is intended to signal to potential users that the org is mothballed, rather than administratively shutting it off without actually deleting files. That is, there will always be some operations that are still possible on archived orgs, but the main "write operation" workflows around changing files, creating new repos, adding users, etc are closed down.

If you've got a few stale orgs hanging around that ought to be put into cryo-sleep, give the archive functionality a try and drop a comment here to let us know how it worked for you. Full docs are here: https://docs.github.com/en/organizations/managing-organization-settings/archiving-an-organization

[matiaskorhonen]

It would be nice if archived organizations would be hidden from the organization dropdown on the dashboard. After all, they're by definition orgs that don't need to be accessed frequently…

[ahpook]

@matiaskorhonen which dashboard do you mean?

[matiaskorhonen]

The one on the home page.

[ahpook]

I confess I have never noticed that before. 😆 Good point, added this to our backlog for post-GA improvements.

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