-
Notifications
You must be signed in to change notification settings - Fork 10
Various small docs improvements #47
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Thomas Steenbergen <[email protected]>
Improved introductory wording for clarity, added a link to GitHub actions documentation to better assist novice users. Signed-off-by: Thomas Steenbergen <[email protected]>
Updated examples to use the main branch and added note advising users to use tagged revisions for production instead of the main branch. This change reduces the need to update the README every time a new revision of the GitHub action for ORT is tagged. Signed-off-by: Thomas Steenbergen <[email protected]>
Signed-off-by: Thomas Steenbergen <[email protected]>
Signed-off-by: Thomas Steenbergen <[email protected]>
Updated copyright year range so it matches NOTICE file. Signed-off-by: Thomas Steenbergen <[email protected]>
8b5348e to
047b546
Compare
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.
Samll changes, more as a security quality of life, the rest is fine
| run: git config --global url.https://github.com/.insteadOf ssh://[email protected]/ | ||
| - name: Checkout project | ||
| uses: actions/checkout@v3 | ||
| uses: actions/checkout@v5 |
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.
Suggestion: if you want to get the benefits of dependabot or similar services to autoupdate actions, pin down the action, inclusive, this is one of items that is considered in scorecard.
So, it would be something like:
actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8There 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.
@heliocastro I followed the actions/checkout docs which clearly shows to use the v5. Think using hash in action versions looks weird especially in examples
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.
| run: git config --global url.https://github.com/.insteadOf ssh://[email protected]/ | ||
| - name: Run GitHub Action for ORT | ||
| uses: oss-review-toolkit/ort-ci-github-action@v1 | ||
| uses: oss-review-toolkit/ort-ci-github-action@main |
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.
Same thing here, avoid @main, which is not seen very well. Consider always tag and pin down
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.
I guess main is intended here as it's this action itself.
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.
@heliocastro I switch to using "main" as I prefer not having to update the README every time we tag a new version of the action. We could also change it to a tag called "latest" similar to how we do things for the ORT docker image. Does that work for you?
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.
So keep with main in this case, but then for external actions, move to pinnning and then is ok
See individual commits for details.