Skip to content

fix: workspaces foreach should take --all by default #5818

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

Conversation

indooorsman
Copy link
Contributor

@indooorsman indooorsman commented Oct 23, 2023

What's the problem this PR addresses?

To fix #5817
...

How did you fix it?

    if (([`all`, `recursive`, `since`, `worktree`] as const).every(opt => this[opt] === undefined)) {
      if (this.from === undefined) {
        this.all = true;
      } else {
        this.recursive = true;
      }
    }

...

Checklist

  • I have set the packages that need to be released for my changes to be effective.
  • I will check that all automated PR checks pass before the PR gets reviewed.

@indooorsman indooorsman force-pushed the issue-5817_fix_workspaces_foreach branch from 626d059 to 9cefe44 Compare October 23, 2023 03:55
@arcanis arcanis mentioned this pull request Oct 23, 2023
arcanis added a commit that referenced this pull request Oct 23, 2023
**What's the problem this PR addresses?**

In preparation for the 4.0 release, this diff adds a blog section to the
website, port the old article, and amorce the writing of the 4.0 release
post.

Fixes #5817
Fixes #5818
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug?]: yarn 4.x yarn workspaces foreach does not take --all by default
1 participant