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: updates after user testing to github.md #362

Merged

Conversation

benroose
Copy link
Contributor

@benroose benroose commented Oct 8, 2024

Description

Edited GitHub Tutorial for required command changes, clarity, and formalizing of language.

Type of change

  • Bug fix (non-breaking change which fixes an issue)

How has this been tested?

Ran through tutorial on a Fedora Linux 39 workstation

Test Configuration:

  • Firmware version: n/a
  • Hardware: Lenovo Thinkpad T580
  • Toolchain: n/a
  • SDK: n/a

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

Edited GitHub Tutorial for required command changes, clarity, and formalizing of language.
Copy link
Member

@jpower432 jpower432 left a 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.

docs/tutorials/github.md Outdated Show resolved Hide resolved
@benroose benroose changed the title Update github tutorial after user testing docs: updates after user testing to github.md Oct 9, 2024
@benroose
Copy link
Contributor Author

benroose commented Oct 9, 2024

@jpower432 numbering is fixed and the PR title/description updated. Please let me know if you need anything further done.

Copy link
Member

@jpower432 jpower432 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@gvauter gvauter left a 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.


1. Open to your GitHub repo in a web browser.
1. Open the remote workflow GitHub repository in a web browser.
Copy link
Member

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.

@@ -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!
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"commit changes" --> "committed changes"?

Copy link
Contributor Author

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."

Copy link
Member

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.
@gvauter gvauter self-requested a review October 17, 2024 01:53
Copy link
Member

@gvauter gvauter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@gvauter gvauter merged commit b9a8caf into RedHatProductSecurity:main Oct 17, 2024
8 checks passed
@benroose benroose deleted the benroose-github-tutorial-1 branch October 17, 2024 14:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants