#3742 Merge multiple project files into multiple project outputs (MIMO) #3800
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
phanlezz
force-pushed
the
feature/3742/mimo
branch
from
b5d73e6 to
3c2d78b
Compare
…ion in main (#3742) Add output project name question to mimo workflow. Restructure mimo workflow to fix potential bug when one name spelling mistake and two correct.
phanlezz
force-pushed
the
feature/3742/mimo
branch
from
b5fccf2 to
d76791d
Compare
|
@Richargh maybe you can try it out :) ? |
|
I will but not right now. I am technically on vacation until Tuesday next week :) |
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Merge multiple project files into multiple project outputs (MIMO)
Issue: #3742
Description
The new -mimo command-line argument allows merging multiple files with the same prefix into separate output files. Files are matched based on their prefix before the first dot (e.g., prj1.sonar.cc.json and prj1.git.cc.json are matched because of the common prj1 prefix). If a file cannot be matched, the program suggests similar file names with a Levenshtein distance of less than 3 to help the user identify potential typos. This ensures a more flexible and error-tolerant merge process.
Definition of Done
A PR is only ready for merge once all the following acceptance criteria are fulfilled: