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

Fix the documentation for bazel fetch --configure #23665

Closed
wants to merge 1 commit into from

Conversation

fmeum
Copy link
Collaborator

@fmeum fmeum commented Sep 19, 2024

With bazel fetch, --configure and --force are now independent and both need to be specified to refetch configure repos. The docs did not reflect this correctly.

Fixes #23639

With `bazel fetch`, `--configure` and `--force` are now independent and both need to be specified to refetch configure repos. The docs did not reflect this correctly.
@fmeum fmeum requested review from Wyverald and meteorcloudy and removed request for gregestren and fweikert September 19, 2024 06:41
@github-actions github-actions bot added team-Documentation Documentation improvements that cannot be directly linked to other team labels awaiting-review PR is awaiting review from an assigned reviewer labels Sep 19, 2024
@fmeum
Copy link
Collaborator Author

fmeum commented Sep 19, 2024

@bazel-io fork 7.4.0

Copy link
Member

@meteorcloudy meteorcloudy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@meteorcloudy meteorcloudy added awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally and removed awaiting-review PR is awaiting review from an assigned reviewer labels Sep 19, 2024
@iancha1992 iancha1992 added the team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website label Sep 19, 2024
@github-actions github-actions bot removed the awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally label Sep 19, 2024
@fmeum fmeum deleted the 23639-fix-force branch September 19, 2024 20:08
fmeum added a commit to fmeum/bazel that referenced this pull request Sep 20, 2024
With `bazel fetch`, `--configure` and `--force` are now independent and both need to be specified to refetch configure repos. The docs did not reflect this correctly.

Fixes bazelbuild#23639

Closes bazelbuild#23665.

PiperOrigin-RevId: 676520136
Change-Id: I07040c743c2b047f8511d1a42ea94d858c520011
iancha1992 pushed a commit that referenced this pull request Sep 20, 2024
With `bazel fetch`, `--configure` and `--force` are now independent and both need to be specified to refetch configure repos. The docs did not reflect this correctly.

Fixes #23639

Closes #23665.

PiperOrigin-RevId: 676520136
Change-Id: I07040c743c2b047f8511d1a42ea94d858c520011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-Documentation Documentation improvements that cannot be directly linked to other team labels team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Xcode 16 incompatibility
3 participants