bazelbuild/bazel

Documentation issue: Migrate bazel sync command information

Open

#11,345 opened on May 10, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Java (4,465 forks)batch import
P3help wantedteam-Documentationteam-ExternalDepstype: documentation (cleanup)

Repository metrics

Stars
 (25,384 stars)
PR merge metrics
 (Avg merge 22d 20h) (77 merged PRs in 30d)

Description

Documentation URL: https://blog.bazel.build/2018/07/09/bazel-sync-and-resolved-file.html https://blog.bazel.build/2018/09/28/first-class-resolved-file.html

There is good information in the linked blogs, but it isn't in the canonical docs.

Contributor guide

Research direction
Read the linked blog posts (https://blog.bazel.build/2018/07/09/bazel sync and resolved file.html and https://blog.bazel.build/2018/09/28/first class resolved file.html) to extract information about the bazel sync command. Identify the appropriate location in the Bazel documentation (likely under the docs directory in the repository) and create or update a markdown file with this information. Follow the project's contribution guidelines to submit a pull request.
Tech stack
None
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitMarkdown
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80