That makes a lot of sense! We already have this on our backlog, I'll see if we can add it soon.

+1

An Archived tag next to the organization name would be awesome!
here: https://github.com/settings/organizations

Labels in lists definitely makes sense. I wonder if for that particular list in settings it would make sense to break archived organizations out into a separate grouping. Any thoughts there?

@mlewinsk-quest @souravcipher We are now showing labels on that page as you suggested. Please take a look at let us know what you think!

Thanks for the hint! I am not familiar with GitHub Enterprise, but if I understand it correctly, these are separate GitHub instances, and not the same as github.com, right? In that case I don't think it would directly help me since these announcements would not be visible to all github.com users who look at an organization, but I can imagine it would be helpful for enterprises.
I wrote my previous comment from the perspective of a user who "consumes" the content of an archived repository or who stumbles across an archived repository and would like to know what happened. I did not write it from the perspective of someone who wants to archive a repository (or organization), and was just hoping that if the support for such an "archiving note" existed, users who archive a repository would use it to explain the reason. But this is of course not guaranteed, but the archiving UI could encourage it, see my original suggestion.

Maybe the importance of such an "archiving note" is not actually that great; it just happened a few times in the past that I stumbled upon an archived repository, and mostly out of curiosity would have liked to understand why the repository was archived. Often this was described somewhere, but not in a uniform way.
It might be interesting to hear the feedback of users who did archive an repository in the past; I would imagine especially the fact that the README is currently the most appropriate way to explain the reason for archiving, but updating the README requires unarchiving is quite cumbersome; which is why I suggested this separate "archiving note" feature.

Sorry for hijacking this discussion if my comment was too unrelated to this new feature of archiving organizations.

these are separate GitHub instances, and not the same as github.com

@Marcono1234 No, not necessarily! There is an on-premise version of GitHub (called GitHub Enterprise Server) but generally, what we refer to as "GitHub Enterprise" is GitHub Enterprise Cloud which is a specific pricing plan on github.com: https://docs.github.com/en/get-started/onboarding/getting-started-with-github-enterprise-cloud

We definitely did discuss adding something like the "archiving note" feature you mentioned. For the moment, I do think just using the organization Readme is probably the most straight forward solution. Just as an idea, maybe we could prompt users to update it before archiving?
This is exactly why we're gathering feedback here so thanks for the input!

Thanks for the information and the correction!

Just as an idea, maybe we could prompt users to update it before archiving?

I don't have an organization where I can currently test this, but according to the documentation (see screenshot there), when archiving a repository it suggests to update the README before. Do you mean the same should be suggested when archiving an organization as well (in case it isn't yet)? Or is your suggestion even going one step further to have an edit link or even a Markdown editor to directly update the README during archiving?

Yes, I think all of these could be viable options to try!

For the time being, we opted to just add some documentation hints to this effect:

You can archive your organization to make it read-only and indicate that it's no longer actively maintained. Prior to archiving, consider updating your organization's profile and README with context about why it's archived. To add an organization-wide README, see "Customizing your organization's profile."

Hi @Katsute - This may be a bug - it looks like all of the repositories in your org are already archived. If you unarchive one (or make a new, active repo), does the button become active?

I tried that before but the button didn't change. My active org @KatsuteDev also has this option disabled.

Creating a new org does however have the archive option available.

@Katsute Could you please check if the button is enabled for you now? I deployed a change yesterday that should correctly assess the billing in some edge cases 🙏🏼

Button works now 👍 ty

Fair point, thanks, I've added it to the backlog - and I appreciate the bump, i'd missed the first notification.

Thanks @ahpook!

@jvaneikeren Question for clarification as I look into this: You can already configure visibility of your organization memberhips so in a sense, it's already configurable 🤔

Maybe just leaving that as is is the better option as it gives users the control on whether they want a specific archived org to still show up?

I did not realize that it's already possible to do this. Is there still a reason to special-case archived orgs, then? I'm inclined to say no.

@lumaxis @ahpook - Thanks for your message. I agree that the ability to determine if an organization is publicly listed on your profile page is an existing capability. However, what I'm requesting here is that the list of organizations that you see when viewing your own profile page (i.e., privately) are limited to those organizations that are not archived. The idea here would be that when viewing your own private profile, you only see a list of organizations that are effectively "active" (i.e., non-archived). I often use the organizations list on my private profile as a way to jump to a specific organization that I'm working in; but as I am an owner of a number of historical/inactive (and now archived) organizations, these archived organizations clutter the list. What I'm trying to avoid doing is having to create a different GitHub user and transfer ownership of the archived organizations to that user just so that the archived organizations won't be included in the list of organizations on my private profile.