Merged
Conversation
Owner
|
Hey, Pavel! This is a great feature! Thank you for the contribution! |
Owner
|
I'll bump a new version today |
Owner
|
v8.1.0 has been released |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Context
Managing group of projects with
dipis hard, imagine having multiple gems with such setupEvery change in sast configuration leads to change in all
dip.ymlamong gems.Related tickets
What's inside
This PR introduces new concept of
modules, modules are stored in.dipfolder. This folder should be synced among group for example with git submodules, so it is stored in one place and synced among group.Each module contains dip configuration so it can be splitted logically, e.g.
Now sasts are managed in one place and can be included via modules.
See more examples in
READMEChecklist: