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

docs: adds in information on how to test PRs in GitHub Codespaces #2617

Merged
merged 18 commits into from Oct 12, 2023

Conversation

shkeating
Copy link
Contributor

@shkeating shkeating commented Oct 4, 2023

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.

image

@shkeating shkeating added type: documentation Improvements or additions to documentation Hacktoberfest labels Oct 4, 2023
@shkeating shkeating requested a review from a team October 4, 2023 15:53
@shkeating shkeating requested a review from a team as a code owner October 4, 2023 15:53
@shkeating shkeating self-assigned this Oct 4, 2023
@shkeating shkeating changed the title [docs] adds in information on how to test PRs in GitHub Codespaces docs: adds in information on how to test PRs in GitHub Codespaces Oct 4, 2023
docs/codespace_pr_reviews.md Outdated Show resolved Hide resolved
docs/codespace_pr_reviews.md Outdated Show resolved Hide resolved
Co-authored-by: Andrew Nelson <andy@andyhub.com>
werdnanoslen
werdnanoslen previously approved these changes Oct 4, 2023
docs/codespace_pr_reviews.md Outdated Show resolved Hide resolved
docs/codespace_pr_reviews.md Outdated Show resolved Hide resolved
docs/codespace_pr_reviews.md Show resolved Hide resolved
docs/codespace_pr_reviews.md Outdated Show resolved Hide resolved
docs/codespace_pr_reviews.md Show resolved Hide resolved
Copy link
Contributor

@kimallen kimallen left a 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!

@shkeating
Copy link
Contributor Author

@werdnanoslen @kimallen thank you both for your feedback! I added more info and made changes to reflect your suggestions :)

kimallen
kimallen previously approved these changes Oct 6, 2023
Copy link
Contributor

@kimallen kimallen left a 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>
Copy link
Contributor

@brandonlenz brandonlenz left a 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!

docs/codespace_pr_reviews.md Outdated Show resolved Hide resolved
docs/codespace_pr_reviews.md Outdated Show resolved Hide resolved
docs/codespace_pr_reviews.md Outdated Show resolved Hide resolved
![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**.
Copy link
Contributor

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

Copy link
Contributor

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!)

docs/design-pr-reviews.md Outdated Show resolved Hide resolved
shkeating and others added 4 commits October 12, 2023 15:50
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>
@shkeating shkeating merged commit ef944f8 into main Oct 12, 2023
8 checks passed
@shkeating shkeating deleted the shk-codespacesdocs-2616 branch October 12, 2023 19:59
@AnnaGingle
Copy link

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.

  1. when the link the storybook will be hosted on is available, you will get a message saying your application is running on port 9009 in the bottom right corner. click the Open in Browser button
  • I understood what you meant after reading it a couple of times but I think this can be workshopped. Maybe something like: When the storybook has started, you get a link to the application running on http://localhost:9009/ or port 9009.
  • I didn't see the screenshot with local host link at first. But when I did I wasn't confused anymore. Might be helpful to move that screenshot between 6&7.
  • I didn't get a notification with the Open in browser button. The other steps worked though.
Screenshot 2023-10-18 at 9 52 57 AM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Hacktoberfest type: documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants