Skip to content
New issue

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

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

Already on GitHub? # to your account

init with multiple repos with the same name #30

Closed
stessaris opened this issue Mar 29, 2022 · 2 comments
Closed

init with multiple repos with the same name #30

stessaris opened this issue Mar 29, 2022 · 2 comments

Comments

@stessaris
Copy link

If there are multiple repos with the same name within different subdirectories, mani init creates an invalid mani.yaml file where keys appear multiple times within the projects object.

A quick solution would be to prepend part of the path to distinguish them in case of repetitions.

@alajmo
Copy link
Owner

alajmo commented Mar 29, 2022

Good catch, and seems like a good enough solution. People can always edit the config later on to their desired name.

alajmo added a commit that referenced this issue May 1, 2022
 ## 0.20.0

 A lot of refactoring and some new features added. There's also some breaking changes, notably to how themes work.

 ### Fix

 - Don't automatically create the `$XDG_CONFIG_HOME/mani/config.yaml` file
 - Fix overriding spec data (parallel and omit-empty) with flags
 - Fix when initializing mani with multiple repos having the same name [#30], thanks to https://github.com/stessaris for finding the bug
 - Omit empty now checks all command outputs, and omits iff all of them are empty

 ### Features

 - Add option to skip sync on projects by setting `sync` property  to `false`
 - Add flag to disable colors and respect NO_COLOR env variable when set
 - Add env variables MANI_CONFIG and MANI_USER_CONFIG that checks main config and user config
 - Add desc of tasks when auto-completing
 - Add man page generation
 - [BREAKING CHANGE]: Major theme overhaul, allow granular theme modification

 ### Changes

 - [BREAKING CHANGE]: Remove no-headers flag
 - [BREAKING CHANGE]: Remove no-borders flag and enable it to be configurable via theme
 - [BREAKING CHANGE]: Removed default env variables that was set previously (MANI_PROJECT_PATH, .etc)
 - Remove some acceptable mani config filenames (notably, those that do not end in .yaml/.yml)
 - Update task and project describe
 - Improve error messages

 ### Internal

 - A lot of refactoring
   - Rework exec.Cmd
   - Remove aurora color library dependency and use the one provided by go-pretty
@alajmo alajmo mentioned this issue May 1, 2022
Merged
@alajmo
Copy link
Owner

alajmo commented May 2, 2022

Should be fixed in 0.20.0, if the issue persists, please open up another ticket.

@alajmo alajmo closed this as completed May 2, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants