Ability to add grouping rules for other repos
See original GitHub issueIs your feature request related to a problem? Please describe.
This project has a really cool feature where you don’t have to maintain multiple versions since a library group is known to use the same version for all of its artifacts. Good example is retrofit2
. All of it’s versions will be simply stored in version.retrofit2
and be shared.
Describe the solution you’d like
The same applies to some of group of artifacts too. refreshVersions
can provide rules functionality to support this. And versions.properties
will become easier to maintain.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Allow organizing/grouping git repositories in a team project
- Ability to assign permissions at each folder level that can be inherited (just like releases). Each team is responsible for dozens of...
Read more >Merge request approval rules - GitLab Docs
Approval rules define how many approvals a merge request must receive before it can be merged, and which users should do the approving....
Read more >Set Git repository permissions - Azure Repos - Microsoft Learn
To set permissions for a specific user, enter the name of the user into the search filter and select from the identities that...
Read more >Repository roles for an organization - GitHub Docs
Repository action Read Triage Write Maintain Admin
Fork the person or team's assigned repositories ✔️ ✔️ ✔️ ✔️ ✔️
Edit and delete their own comments...
Read more >Organize groups for your repositories | Bitbucket Cloud
You can use user groups to provide other users access to your repositories. When you create a new repository and specify your workspace...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@joharei Probably a bug, though in future versions, we might have a different behavior as we might stop auto-removing unused entries, just adding a warning/info comment instead.
I’ve explained how it works here:
https://github.com/jmfayard/refreshVersions/issues/356#issuecomment-843276157