-
Notifications
You must be signed in to change notification settings - Fork 10
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: updates after user testing to github.md #362
docs: updates after user testing to github.md #362
Conversation
Edited GitHub Tutorial for required command changes, clarity, and formalizing of language.
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.
@benroose Thanks for the PR! Just one minor issue I found.
@jpower432 numbering is fixed and the PR title/description updated. Please let me know if you need anything further done. |
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.
LGTM
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.
Two very minor feedback items, otherwise LGTM.
docs/tutorials/github.md
Outdated
|
||
1. Open to your GitHub repo in a web browser. | ||
1. Open the remote workflow GitHub repository in a web browser. |
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.
nitpick: maybe remove "workflow"? Just to avoid any confusion that there may be more than 1 remote repo involved.
docs/tutorials/github.md
Outdated
@@ -104,6 +130,6 @@ Now it's time to run our first trestlebot action! We will go ahead and create o | |||
|
|||
6. Click `Run Workflow` | |||
|
|||
Once the workflow has completed you should have a new Pull Request containing the files trestlebot generated for the component definition. After reviewing the files you can go ahead and merge the PR! | |||
Once the workflow job has completed, there will be a new Pull Request containing the files trestlebot generated for the component definition. After reviewing the commit changes, the Pull Request can then be merged into the main branch! |
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.
"commit changes" --> "committed changes"?
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.
Hi @gvauter, sorry for delay. Those minor changes are now committed in the merge request. Please let me know if you see any other fixes needed prior to giving it your "go ahead."
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.
Looks good to me, thanks @benroose!
Minor documentation changes for clarity.
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.
lgtm
Description
Edited GitHub Tutorial for required command changes, clarity, and formalizing of language.
Type of change
How has this been tested?
Ran through tutorial on a Fedora Linux 39 workstation
Test Configuration:
Checklist