Summary
Repositories created by Vizably should automatically be prefixed with viz_.
For example:
viz_scans
viz_reports
viz_accessibility-results
Problem
Currently, repositories created by Vizably do not have a consistent naming convention. This makes it easier to accidentally interact with user-owned repositories that were not created or intended for Vizably.
It is also not immediately obvious which repositories belong to Vizably.
Proposed Solution
When Vizably creates a repository, prepend viz_ to the repository name.
Benefits:
- Prevents accidentally reading from or writing to unrelated repositories.
- Makes Vizably-managed repositories immediately recognizable.
- Simplifies filtering, debugging, and future maintenance.
- Provides a clear namespace for repositories managed by the application.
Acceptance Criteria
- All newly created repositories use the
viz_ prefix.
- Repository lookups and validations account for the new naming convention.
- Existing functionality continues to work with the updated repository names.
- Documentation and any relevant UI text are updated to reflect the naming convention.
Summary
Repositories created by Vizably should automatically be prefixed with
viz_.For example:
viz_scansviz_reportsviz_accessibility-resultsProblem
Currently, repositories created by Vizably do not have a consistent naming convention. This makes it easier to accidentally interact with user-owned repositories that were not created or intended for Vizably.
It is also not immediately obvious which repositories belong to Vizably.
Proposed Solution
When Vizably creates a repository, prepend
viz_to the repository name.Benefits:
Acceptance Criteria
viz_prefix.