Skip to content
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

[shopsys] docker-sync now does not exclude project-base/docs in monorepo #1172

Merged
merged 1 commit into from Jul 1, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
1 change: 0 additions & 1 deletion docker/conf/docker-sync-win.yml.dist
Expand Up @@ -17,7 +17,6 @@ syncs:
'docker',
'nbproject',
'project-base/docker',
'project-base/docs',
'project-base/kubernetes',
'project-base/node_modules',
'project-base/var/cache',
Expand Down
1 change: 0 additions & 1 deletion docker/conf/docker-sync.yml.dist
Expand Up @@ -13,7 +13,6 @@ syncs:
'docker',
'nbproject',
'project-base/docker',
'project-base/docs',
'project-base/kubernetes',
'project-base/node_modules',
'project-base/var/cache',
Expand Down
1 change: 1 addition & 0 deletions docs/contributing/upgrading-monorepo.md
Expand Up @@ -38,6 +38,7 @@ Typical upgrade sequence should be:
- eg. you can use `tests-unit` to run unit tests in the whole monorepo instead of running `tests-unit`, `tests-packages` and `tests-utils`
- you can even use coding standards subtargets in the whole monorepo, such as `ecs`, `eslint-fix`, etc.
- read [the new guidelines for phing targets](/docs/contributing/guidelines-for-phing-targets.md) before suggesting changes via pull requests
- remove `'project-base/docs',` line from your `docker-sync.yml` ([#1172](https://github.com/shopsys/shopsys/pull/1172))

## [From v7.2.0 to v7.2.1]

Expand Down