Skip to content

Why does GitHub recommend closing issues before archiving a repository? #22554

Answered by CleanCut
pdpinch asked this question in New to GitHub
Discussion options

You must be logged in to vote

Thanks for asking!  I asked around in engineering and found the person who came up with that recommendation.

According to him, there was a point in time when we were considering whether to auto-close all issues and pull requests when a repository was archived.  We felt (and still feel) that not closing issues and pull requests before archiving a repository has drawbacks, foremost among them:

  • People often assume that open issues and pull requests will eventually be acted upon

  • The person who opened the issue will forever have it listed as open, and will be unable to close it themselves.

In the end, it was decided to make it a recommendation rather than an automatic behavior.  I submit…

Replies: 4 comments 8 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
7 replies
@allan2
Comment options

@CleanCut
Comment options

@spenserblack
Comment options

@ghost

This comment was marked as off-topic.

@ghost

This comment was marked as off-topic.

Answer selected
Comment options

You must be logged in to vote
1 reply
@spenserblack
Comment options

Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
7 participants