-
Notifications
You must be signed in to change notification settings - Fork 3
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 README.md with Getting Started and design info #91
docs: updates README.md with Getting Started and design info #91
Conversation
Signed-off-by: Jennifer Power <[email protected]>
README.md
Outdated
The workflow to update content consists of the following steps: | ||
|
||
1. From a user's branch, modify and commit a markdown or json file within the workspace. (Most updates will be made to markdown files.) | ||
2. A user submits a pull request to add their changes to the workspace's master 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.
Suggest replacing master
with main
to align with step 4.
docs/design.md
Outdated
|
||
The `create-new` workflow is triggered manually by going to the Action tab. This creates a new OSCAL profile in the trestle workspace. A new branch is created and a pull request is opened. | ||
|
||
#### AutoFix |
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.
Would it ease understanding if this was titled "AutoSync" to align with the trestle-bot terminology?
Signed-off-by: Jennifer Power <[email protected]>
Signed-off-by: Jennifer Power <[email protected]>
@gvauter Please take another look. Due to changes in the CI files, this might require some testing on my fork as well. |
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
Updates docs to use the same structure as
oscal-component-definitions
. This replaces the manual tutorial (which is out of date) with a tutorial about how to interact with the repostiroy content through GitHub andtrestle-bot
actions. In depth approach information (like https://github.com/RedHatProductSecurity/oscal-component-definitions/blob/main/docs/design.md) is also added.Testing CI naming changes