@esteban-url please see the PR I submitted against your fork. I performed basic edits and left a couple PR comments.

General question: What is the recommended way to contribute/edit files associated with somebody else's PR?

Here's how I did it (as a noob that is figuring it out)... Created my own fork of redwoodjs/redwood, checked out the test-in-github-actions branch, renamed it, edited the article, pushed it to my forked repo, then submit a PR to esteban-url.

Seems a bit round-about, but I think it works. I also tried to push commits directly (instead of creating a PR, but I got 403 errors).

Thanks for helping me work through the GitHub flow!

@esteban-url looks great so far! thanks for all the hard work.

@keithtelliott

General question: What is the recommended way to contribute/edit files associated with somebody else's PR?

Here's how I did it (as a noob that is figuring it out)... Created my own fork of redwoodjs/redwood, checked out the test-in-github-actions branch, renamed it, edited the article, pushed it to my forked repo, then submit a PR to esteban-url.

Seems a bit round-about, but I think it works. I also tried to push commits directly (instead of creating a PR, but I got 403 errors).

This is generally the way to do it.

I also tried to push commits directly (instead of creating a PR, but I got 403 errors).

Unless you have been explicitly granted authorized access to a repo you don't own, this is the expected behavior.

@keithtelliott thanks a bunch! I check out your PR, and look into granting you the necessary access to my repo.

@virtuoushub Thanks for checking out the PR and provinding the answers to Keiths questions!

@esteban-url I worked through the How To and ran my unit tests within GitHub Actions. It just worked! Your technical description successfully guided me through the required steps. So, I did not add/adjust the technical details.

I did, however, add a callout note mid-way through, and a summary conclusion at the end. My goal: encourage the reader.

As with my prior contribution, I submitted a PR to you, on your esteban-url fork. Please review/edit/merge as you see fit.

Looks like we're getting a build error; trying to find out what's causing it

thanks @jtoar, I saw the error on the first commit, but thought it was maybe one of those "expected" errors.

At the time I removed emojis and something else. I can help trying to figure it out, but how can I test this locally?

@esteban-url the errors you get from docusaurus locally aren't super great; you just need a mental model of what's going in the file. So this file is MDX, which means it's markdown and react. But really it's all react—so a build error usually means there's a react error. In this case it's just that you forgot to close the img tags: d3504cc

Thanks! That makes a lot of sense. I'll keep it in mind for my next docs PR!

@esteban-url reading through now and making some edits I'll push up as I go—great stuff! I'll focus on getting this merged today.

Thanks! yeah, feel free to edit anything.

Again, great stuff @esteban-url! And thanks for letting me have at it a bit. The diff of edits may look large, but it was just polishing, made easier by the great structure that was already there. A few tips for the future:

• use relative links for other redwood docs. it lets docusaurus do it's thing
• for code blocks, you can use a title "attribute" as the de facto place for the the file's title