-
Notifications
You must be signed in to change notification settings - Fork 17
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
Reduce redundancy #3
Comments
Submodule system is based on a commit hash so no one should have difficult with this form of submodule. |
As for me, everything is fine with few rules files in the repo. What benefits will we get if we switch to branches? I can see only new difficulties with updating. |
Аналогично, не вижу нужды увеличивать сложность в сторону разделения отдельных веток. Я бы предложил вносить все изменения в основной yml-файл, а json генерить автоматически, добавив таск для Rake, или что вы там в Ruby используете, чтобы любой разработчик, который внес изменения, мог дернуть его быстренько и пушнуть, не заморачиваясь. |
Rakefile is added in 8a0371c. You can generate the JSON rules file |
As I understand, we continue to maintain repository in current state. |
We have got a small redundancy after merge #2. I propose to split the master branch into two independent parallel branches named Json and Yaml. After splitting one can use the branch they need.
The text was updated successfully, but these errors were encountered: