Hey guys, I’m using seed.run with my lerna worksp...
# help
d
Hey guys, I’m using seed.run with my lerna workspace and everytime I make a change to readme files / other general config files in my project, I see that seed.run is deploying the service. I’m wondering why it is necessary to deploy again instead of simply skipping it...
Copy code
INFO: Checking for changes in the images service using lerna...
1.32 s
$ lerna ls --since 5841c598eef416cd0757681e6fa1f70f6b890136 --json -all
lerna notice cli v3.22.1
lerna info versioning independent
lerna info ci enabled
lerna notice filter changed since "5841c598eef416cd0757681e6fa1f70f6b890136"
lerna info Looking for changed packages since 5841c598eef416cd0757681e6fa1f70f6b890136
[]
lerna success found 0 packages
Checking for file changes that don't belong to any packages...
Need to deploy since the following files have been updated:
  README.md
Learn more about monorepo deployments - seed.run/docs/deploying-monorepo-apps
f
Hey @Dani Akash, sorry about the late follow up.
So based on the Lerna algorithm:
2. If there are other file changes in the Git log that don’t belong to any packages in your Yarn Workspaces, then we deploy the current service
So in this case, since README.md doesn’t belong to any service, SEED assumes that it is a common file shared by all services. Hence all services will be deployed.
But I can see that changes in README.md should be ignore.
It’s actually on our roadmap to add support for ignored files. So you can list README.md and other config as ignored files. And they won’t be accounted for when checking which services need to be deployed.
d
This is great. Ignored files will help us save a lot of build minutes. Is the roadmap available publicly?
f
Not at the moment. But it’s something we want to make public when we get a chance.