Issues

Issue #6782 duplicate

Repository Tagging

Sterling Hamilton
created an issue

Preface, I didn't know the proper channel to send this on through, but I figured I'd give it a shot placing it here.

As a user, owning multiple repositories is a very real possibility. Organizing these repositories is a chore. As an agency user having hundreds of repositories is expected. A way of tagging repositories would help solve this problem. Currently my Team has 55 repositories. We are naming them in such ways as [wordpress] [theme] newproject.com or [custom] [platform] projectname.

This is currently allowing us to filter the projects using existing methods within the system and finding types of projects such as codebases or libraries is easy through the user dashboard.

The downside is that this leads to bloated repository names and frequent renaming of repositories.

Request: Add tagging to repositories. A user would go into a repository and have a box somewhere on the screen that would allow for comma separated tags.

The request is minor at this time, but as we proceed throughout the year, 200 repositories is a reality we expect to have to deal with. Then searching through them will be cumbersome and may require elevation.

Thanks for your time!

Comments (4)

  1. Christopher Crevling

    Tagging would be a great way to allow for people to manage multiple projects. It could also allow for people who get added onto a project an easy way to pull that information even if they have over 100 repositories laying around. This would be a very cool and efficient way to represent our repository systems between agencies and humans.

  2. Log in to comment