Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pluggable naming strategies #42

Open
fredcooke opened this issue Nov 25, 2019 · 1 comment
Open

Pluggable naming strategies #42

fredcooke opened this issue Nov 25, 2019 · 1 comment

Comments

@fredcooke
Copy link
Collaborator

Currently works with opinionated maven-style repo naming, a flat option would make this more globally useful. In branchout settings just have a model: or naming: field with flat, maven, etc in it. Unknown values should print acceptable values on failure.

@fredcooke
Copy link
Collaborator Author

Thinking about this more recently. I actually do a groups style layout myself for my own stuff that I'd like to use this with, however the group is not included in the repos because it doesn't make sense to. What would make sense is a .branchoutgroups file IN each repo and branchout can clone the repo to eg .branchout-tmp and then see what's there on the default branch (whatever it's called :-p) and mkdir/mv repo as needed. This would be super nice, I'd start using it immediately with just that change.

Could be driven by a top level Branchoutfile option layoutStrategy or similar eg groupByRepoName or groupByDotBranchoutgroups or similar? CC @stickycode

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant