We have many (over 1000) git repositories that need to be managed similarly.
For example, we set the 'auto close branches' to master in the vast majority of them. I recently wanted to add additional branches to track, but this requires editing each repo on its own. Having a diffusion.edit endpoint would be helpful, but it would be even better if we could have a single configuration location and set "this repo uses this configuration"
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | epriestley | T9287 Working with many repositories | ||
| Resolved | eadler | T10415 Make it easier to manage large number of repositories with similar configuration via the web ui |
Event Timeline
Comment Actions
Do you legitimately have several distinct "profiles"? What differs between them?
Which options other than "autoclose" would you want to be part of the profiles?
Comment Actions
We have 2 distinct profiles and a few one-offs.
Ideally the following would be managed: Policies, Text Encoding, Branches, Actions. The remainder are templatized but obviously differ from repo to repo.
An alternate solution might be to "batch edit" repositories and make similar changes across them. My concern with this approach is that it would be easy to forget that a repo is a one-off in some way.
Comment Actions
Sorry, I'm still not sure I quite understand the specific use cases for this feature that you anticipate.
Maybe a better way to put it is: the feature you propose is tremendously complex and will require something like a month of dedicated work to implement. If we had it, and also had "Create Similar Repository..." (T6722), meaningful API access (T10337, T5873, so you could do updates via the API) and EditEngine (so you could create "New Type A Repository...", "New Type B Repository..." forms with prefilled/locked defaults), how many hours of work do you anticiapte profiles/web bulk would save you per year over clone/api/forms alone?
Comment Actions
To be clear: I was trying to describe my problem, not ask for a specific solution. EditEngine for creation would help a lot but I was focused on editing. I guess T10337 would actually solve the issue, though not in the web UI.