Add better support for archiving repositories.
Review Request #6043 — Created July 1, 2014 and submitted
Archiving had issues before where an archived repository's path would
still conflict with a newly created repository. This confused a lot of
people using RBCommons, and required some manual work on our end to fix.Now, we store a flag indicating that a repository is archived, and we
store the archived timestamp. The timestamp becomes part of the
unique_together
for the path, preventing that from conflicting.
Unit tests pass.
Description | From | Last Updated |
---|---|---|
'time' imported but unused |
reviewbot |
- Change Summary:
-
Remove an unused import.
- Commit:
-
925e9be931e7ab8cf9bec841929be15dcd4128a59b54c7d59556592302550aef8a6566802a20e043
-
Tool: Pyflakes Processed Files: reviewboard/webapi/resources/repository.py reviewboard/scmtools/models.py reviewboard/scmtools/tests.py reviewboard/webapi/tests/test_repository.py reviewboard/scmtools/evolutions/repository_archive.py reviewboard/scmtools/evolutions/__init__.py Tool: PEP8 Style Checker Processed Files: reviewboard/webapi/resources/repository.py reviewboard/scmtools/models.py reviewboard/scmtools/tests.py reviewboard/webapi/tests/test_repository.py reviewboard/scmtools/evolutions/repository_archive.py reviewboard/scmtools/evolutions/__init__.py