While I don't expect many users to rely on this, I'm a bit concerned about another backward compatibility break.
Maybe better introduce --no-deps to mimic same option used by up?
Also, to avoid code duplication, could define a func to disable all services but selected ones

Codecov Report

Base: 76.98% // Head: 75.79% // Decreases project coverage by -1.19% ⚠️

Coverage data is based on head (91f7dcb) compared to base (8c39b5b).
Patch has no changes to coverable lines.

@@            Coverage Diff             @@
##               v2   #10044      +/-   ##
==========================================
- Coverage   76.98%   75.79%   -1.20%     
==========================================
  Files           2        2              
  Lines         252      252              
==========================================
- Hits          194      191       -3     
- Misses         51       53       +2     
- Partials        7        8       +1     

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

While I don't expect many users to rely on this, I'm a bit concerned about another backward compatibility break.

Fair point, I can definitely move it to a --no-deps flag instead, but this would be inconsistent with docker-compose pull. What about setting the value of this flag to true instead and let users pass --include-deps=false instead?

Also, to avoid code duplication, could define a func

Sure, can you point me to a good place to do this? I'm not familiar with this codebase to select a proper location myself.

I didn't noticed --include-deps flag existed for pull, makes more sense now. Both should be aligned. Minor compatibility break probably is acceptable from this point of view.

you can just extract https://github.com/docker/compose/blob/v2/cmd/compose/up.go#L57-L66 into a func inside up.go and call it from both command - by the way, can also use it for pull where code already is duplicated

also need to regenerate docs to reflect new flag using make docs

@ndeloof not sure why you meant up.go, I extracted the function in pull.go - if you really wanted it to be in up.go I can change it.

Otherwise, this should be ready.