What archiving an item actually does
A GitHub Project fills up fast.
Finished tasks, stale ideas and abandoned experiments pile up next to the work you are actually doing.
At some point you face a choice: archive those items or delete them.
The two options look similar from your board, but they behave very differently once you click confirm.
This guide walks through what each option actually does, when each one makes sense, and how to get items back if you change your mind.
By the end you will have a simple rule of thumb you can apply to any cluttered project.
Archiving removes an item from your project views, but keeps the context about that item in the project.
The item disappears from your table, board and roadmap, so your active views stay clean.
It is not gone, though.
GitHub keeps archived items available to restore, and you can bring them back whenever you want.
Think of archiving as moving work into a labeled box in the storeroom.
You cannot see it on the shelf anymore, but you know exactly where to look if you need it again.
Archiving is also the option that supports automation.
You can configure your project's built-in workflows to automatically archive items that meet certain criteria, such as items marked done.
That means you can set up a rule once and let finished work tidy itself away, instead of manually sweeping your board every week.
What deleting an item actually does
Deleting removes the item from the project entirely.
There is no archive page to visit and no restore button waiting for you.
Once you confirm the deletion, the item and its context in that project are gone.
It is worth pausing on what that means in practice.
If an item held notes, links or a record of why you made a decision, deleting it erases that record from the project.
If you later need to explain why a feature was dropped or when a task was finished, you may have nothing to point to.
Deletion is a separate question from deleting the underlying issue itself.
Removing an item from a project does not delete the issue from its repository.
If you want to delete an issue permanently, that is a different action with its own permission rules, which we cover below.