docs: update readme#32084
Conversation
gkalpak
left a comment
There was a problem hiding this comment.
In general, I believe it is better to use markdown as much as possible and only resort to HTML if absolutely necessary.
01bb23a to
83b9ef1
Compare
|
Currently broken ... can't get the second image to show up. |
|
@sjtrimble @gkalpak this seems nearly complete is there a blocker for this, If needed I can help on this |
|
@ajitsinghkaler If you'd like to help -> could you help me to get the second image to show up? I think the |
|
@sjtrimble can you please tell me which image is not loading as far as I can see al img tags are loading perfectly on my pc |
83b9ef1 to
0d9ee00
Compare
|
I think this is ready for another review :) @ajitsinghkaler @gkalpak |
There was a problem hiding this comment.
Nice! Almost lgtm 🎉
To fix CI (failing job), you need to add the newly added docs/images/ directory to a code-owner group. Currently, the README.md file is owned by dev-infra (as are most of the files in docs/), so it makes sense to assign docs/images/ to dev-infra too.
To do that, you need to add a new line in .pullapprove.yml:
'docs/TRIAGE_AND_LABELS.md',
+ 'docs/images/**',
'goldens/*',1d259a5 to
55b4a09
Compare
|
@gkalpak Okay, I think I covered the remaining items. Let me know if you see anything else. We'll see how the CI does :) |
|
It looks like this PR is almost ready for merge! @gkalpak @sjtrimble, could you please rebase this PR and resolve the conflict, so that we re-run the CI and proceed with the merge? Thank you. |
dfeeeca to
fcf3dc0
Compare
fcf3dc0 to
0c2a17e
Compare
|
Rebased and resolved conflicts. I also updated the badges (see images below for the difference):
|
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |



PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Updated README file to improve usability
Does this PR introduce a breaking change?