Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature: archive repository #1353

Closed
ghost opened this issue Mar 21, 2017 · 8 comments
Closed

feature: archive repository #1353

ghost opened this issue Mar 21, 2017 · 8 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Milestone

Comments

@ghost
Copy link

ghost commented Mar 21, 2017

I have some repositories uploaded to my gitea installation which are not used any longer but to which I need read access. We should implement a feature which makes it possible to "archive" a repository so you cannot push, create issues, comment or do anything else which may change it. There should be a notice "This project is archived." but you should be able to access everything in a read-only mode.

This prevents these repos from accidental pushes and a visitor will see that this repo is not maintained.

@lunny lunny added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Mar 22, 2017
@lunny lunny added this to the 1.x.x milestone Mar 22, 2017
@bkcsoft
Copy link
Member

bkcsoft commented Apr 18, 2017

Should be fairly simple to just add a Archived-flag in the DB :)

@monkeyhybrid
Copy link

GitLab has such a feature and if I remember correctly, as well as making the repo read-only, it hides it from the dashboard and removes it from searches too, which keeps things really tidy. This is a real bonus when you have many more 'stale' repos than active ones. And of course, you can always un-archive it in the future if you wish to continue work on the repo.

GitHub does something similar, but doesn't remove the archived repo from the dashboard (which can be annoying when you have lots of archived repos).

As it stands now in Gitea, I currently rename my stale repositories, adding -Archive-2017 to their name, for example, but this still leaves them cluttering the dashboard and obviously does nothing to make them read-only. I'd love for Gitea to offer archive functionality in the same manner as GitLab does it. If I can help by providing any further details or testing, I will gladly do so.

@lafriks
Copy link
Member

lafriks commented May 9, 2018

@monkeyhybrid what do you mean with dashboard?

@monkeyhybrid
Copy link

@lafriks In the Gitea web app, you have a Dashboard link at the top. Clicking this brings up a page showing recent activity in the main content area, and a list of repositories on the right hand side. It may be called something else in GitHub, although I think the same in GitLab, but roughly the same thing exists in both.

A list of repositories is also shown when clicking on Explore.

If an archive feature is added to Gitea, as well as making a repo read-only, it would be nice if archived repositories are not shown in these lists, and search results, or at least have an option to include / exclude archived repositories. This would remove a lot of clutter for those of us with lots of stale repositories (that we don't want to delete).

@AndyHee
Copy link

AndyHee commented Jul 6, 2018

The possibility of irreversibly setting a repo to read-only would definitely be a very useful feature for archiving purposes.

@bram-dingelstad
Copy link

This feature would mean a world of difference for me, I have a lot of smaller ideas that I want to keep around but not cluttering the rest of the application/repositories!

@stale
Copy link

stale bot commented Jan 11, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Jan 11, 2019
@lunny lunny modified the milestones: 1.x.x, 1.8.0 Jan 12, 2019
@lafriks lafriks added issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented and removed issue/stale labels Jan 13, 2019
@adelowo
Copy link
Member

adelowo commented Feb 10, 2019

This can be closed

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Projects
None yet
Development

No branches or pull requests

8 participants