myriad currently duplicates the global content .syncignore and .challengifyignore files to each individual temporary challenge repo before the sync occurs
the goal is to keep the ignore rules active during the transition before each rules are moved in the corresponding content challenge subdirectory
the path relative to each challenge is correctly substracted from the rules
the globbing patterns such as **/test.md are correctly handled
but the README.md which should reference only the readme at the root of the global content directory are incorrectly duplicated as is while they should be removed
the consequence is that challengify interprets the README.md rule at the root of data-solutions as only affecting the root readme while myriad incorrectly duplicates this rule for each challenge and all the internal repo readmes end up not synced
myriad currently duplicates the global content
.syncignoreand.challengifyignorefiles to each individual temporary challenge repo before the sync occursthe goal is to keep the ignore rules active during the transition before each rules are moved in the corresponding content challenge subdirectory
the path relative to each challenge is correctly substracted from the rules
the globbing patterns such as
**/test.mdare correctly handledbut the
README.mdwhich should reference only the readme at the root of the global content directory are incorrectly duplicated as is while they should be removedthe consequence is that
challengifyinterprets theREADME.mdrule at the root ofdata-solutionsas only affecting the root readme whilemyriadincorrectly duplicates this rule for each challenge and all the internal repo readmes end up not synced