doc: improve core rules introduction #3100
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
A rendered version of the graph could be viewed here https://github.com/sluongng/rules_go/blob/sluongng/pretty-graph/docs/go/core/rules.md#introduction |
Added a visualization for sample Bazel Build Graph when using rules_go core rules to help new users better understand the relationship between them. The graphic was created with Excalidraw and exported to SVG for display.
sluongng
force-pushed
the
sluongng/pretty-graph
branch
from
5e017d9
to
61bc294
Compare
linzhp
approved these changes
Apr 1, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a visualization for sample Bazel Build Graph when using rules_go
core rules to help new users better understand the relationship between
them.
The graphic was created with Excalidraw and exported to SVG for display.
What type of PR is this?
What does this PR do? Why is it needed?
Improve documentation for new users of rules_go
Which issues(s) does this PR fix?
Other notes for review
I am open for feedbacks regarding how the graphic should look.
I have included an buildgraph.excalidraw file so that anyone can open this up in https://excalidraw.com/ and edit