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

Calculate the bazel directory based on the path of bazel-dev.sh #22577

Closed
wants to merge 1 commit into from

Conversation

matts1
Copy link
Contributor

@matts1 matts1 commented May 29, 2024

Instead of hardcoding the ~/os-bazel directory, calculate the bazel directory based on the path of the script.

This should make setup simpler, and also allow you to work with multiple bazel checkouts at the same time by simply calling the corresponding bazel-dev.sh script.

…irectory based on the path of the script.

This should make setup simpler, and also allow you to work with multiple bazel checkouts at the same time by simply calling the corresponding bazel-dev.sh script.
@github-actions github-actions bot added the awaiting-review PR is awaiting review from an assigned reviewer label May 29, 2024
@sgowroji sgowroji added the team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website label May 29, 2024
@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 Jun 4, 2024
@copybara-service copybara-service bot closed this in 4582011 Jun 4, 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 Jun 4, 2024
@matts1 matts1 deleted the dev_sh branch June 4, 2024 23:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.

3 participants