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
docs: adds in information on how to test PRs in GitHub Codespaces #2617
Conversation
Co-authored-by: Andrew Nelson <andy@andyhub.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love this codespace option. A couple comments and suggestions. Otherwise looks great!
… message or it goes away before you click it.
@werdnanoslen @kimallen thank you both for your feedback! I added more info and made changes to reflect your suggestions :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good! I made one suggestion for a content change, but approving! Thanks for putting this together!
Co-authored-by: Kim Allen <kim@truss.works>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Found a couple typos we should handle before merging. This is really great!
![storybook running in codespaces dev environment](https://github.com/trussworks/react-uswds/assets/59394696/cdfc67de-711f-43c2-928a-284158744f1f) | ||
|
||
11. proceed as if you were running the PR on your own machine. hooray! | ||
12. When your review is complete, you should delete the codespace. There are costs associated with storing codespaces. **You should therefore delete any codespaces you no longer need**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bummer that this isn't free for open source repositories, but I understand why. Looks like costs are pretty minimal, and free for the first (up-to) 60 hours per month.
This is definitely something we should still be vigilant about. It's easy to "leave the stove running" on this switching contexts to and from ReactUSWDS
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nothing to change on the PR, the step is explicit, just a thought I had while reading and learning about Codespaces (I haven't used them before!)
Co-authored-by: Brandon Lenz <15805554+brandonlenz@users.noreply.github.com>
Co-authored-by: Brandon Lenz <15805554+brandonlenz@users.noreply.github.com>
Co-authored-by: Brandon Lenz <15805554+brandonlenz@users.noreply.github.com>
Co-authored-by: Brandon Lenz <15805554+brandonlenz@users.noreply.github.com>
Hello! Here is some feedback on the documentation as promised. I could only find 1 thing that might need some clarity. I am learning your superpower is documentation.
|
Summary
Adds info doc about using Codespaces to review PRs so you can check out changes and run them on a dev server without having to on your machine, reducing context switching and lowering the barrier to PR reviews.
Adds reference in design PR review doc to this page
Related Issues or PRs
docs: add design PR review documentation #2615
How To Test
Int he changed files view, click the icon in the upper right of the md file for
Display rich diff
. This will let you preview the markdown file. Follow the steps in the process and make sure I have outlined the process well enough for you to figure it out.