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

document "build -c <...>" option: have a short to long list correspondence somewhere #4062

Closed
excavador opened this issue Nov 9, 2017 · 4 comments
Labels
P3 We're not considering working on this, but happy to review a PR. (No assignee) stale Issues or PRs that are stale (no activity for 30 days) 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 type: documentation (cleanup)

Comments

@excavador
Copy link

documentation about "-c" option missed:
https://docs.bazel.build/versions/master/command-line-reference.html#build

Option was mentointed here bazel-contrib/rules_go#993

@ianthehat
Copy link
Contributor

This is actually documented, the easiest way to find the short form documentation at the moment is to search for [-c] (for any of the single letter options), but that is something you kind of have to just know. Maybe a table of short to long forms somewhere would be helpful?

@excavador
Copy link
Author

Maybe a table of short to long forms somewhere would be helpful?

Definitely! It would be awesome.
Just imagine how to user search information - find link to command line reference and make search on the page.

@damienmg damienmg changed the title document "build -c <...>" option document "build -c <...>" option: have a short to long list correspondence somewhere Nov 11, 2017
@jin jin added team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website untriaged labels Sep 3, 2019
@philwo philwo added the P3 We're not considering working on this, but happy to review a PR. (No assignee) label Dec 8, 2020
@philwo philwo removed the untriaged label Feb 8, 2021
@ShreeM01 ShreeM01 added the team-Documentation Documentation improvements that cannot be directly linked to other team labels label Dec 5, 2022
Copy link

github-actions bot commented Feb 9, 2024

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 90 days unless any other activity occurs. If you think this issue is still relevant and should stay open, please post any comment here and the issue will no longer be marked as stale.

@github-actions github-actions bot added the stale Issues or PRs that are stale (no activity for 30 days) label Feb 9, 2024
Copy link

github-actions bot commented May 9, 2024

This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please post @bazelbuild/triage in a comment here and we'll take a look. Thanks!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 We're not considering working on this, but happy to review a PR. (No assignee) stale Issues or PRs that are stale (no activity for 30 days) 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 type: documentation (cleanup)
Projects
None yet
Development

No branches or pull requests

6 participants