hey all i want to organize my projects docs inside the project folder, for example:
- projects
- a
- docs
- b
- docs
i'm using poly/projects-to-deploy to determine changes and deployments
i dont want to deploy a project (and its dependencies) when the docs change
how can i achieve that?
is there some "poly.ignore"?
i want to avoid creating a root folder "docs" with sub folders duplicated as the projectsthanks for your reply the "project-to-deploy" tracks changes via git on the project folder and its dependencies (components + bases)? or just what's under src / resources?
If you do poly diff it will call a git command, see example https://cljdoc.org/d/polylith/clj-poly/0.3.32/doc/git:
bases/cli/deps.edn
bases/cli/resources/cli/.keep
bases/cli/src/se/example/cli/core.clj
bases/cli/test/se/example/cli/core_test.clj
build.clj
components/user/deps.edn
components/user/resources/user/.keep
components/user/src/se/example/user/core.clj
components/user/src/se/example/user/interface.clj
components/user/test/se/example/user/interface_test.clj
deps.edn
development/src/dev/lisa.clj
projects/command-line/deps.edn
workspace.edn
Based on this output, it recognises components/, bases/ , and so on. Here it will treat the user component as changed for example.
If you have a changed file in e.g. projects/myproject/doc if will identify myproject as changed. The fix is to list directories and/or files in a key in workspace.edn and then exclude these (probably with some kind of regex). That would solve your problem.i see
so instead of using poly/projects-to-deploy you suggest using diff and filter them out based on the workspace edn key
did i get it right?
No, I mean when we have support for excluding files from the calculation that returns the changed files, commands like poly ws get:changes:changed-or-affected-projects will also work correctly, because everything is based on that git diff under the hood.
ohh i see.. ok thanks!
Do you want me to create an issue?
no i will do it i will find time in the upcoming days for an issue and maybe a pr, depends how difficult it will be
Sounds good.
We don't have support for that, but it wouldn't be too hard to support. You can create an issue if you want, and describe the needs.