Are there any risky areas that deserve extra testing?
References
Comments
Contributor's Checklist
PR process:
[ ] If this is an important user-facing change, PR or related issue the CHANGELOG label been added to this PR. Note: items with this label will be added to the CHANGELOG at a later time
[ ] If this includes an internal dependency change, a link to the diff is provided
[ ] The docs label has been added if this introduces a change that needs to be updated in the user docs?
[ ] If any Python requirements have changed, the updated requirements.txt files also included in this PR
[ ] Opportunities for using Google Analytics here are noted
[ ] All user-facing strings are translated properly
[ ] The notranslate class been added to elements that shouldn't be translated by Google Chrome's automatic translation feature (e.g. icons, user-generated text)
[ ] All UI components are LTR and RTL compliant
[ ] Views are organized into pages, components, and layouts directories as described in the docs
[ ] Users' storage used is recalculated properly on any changes to main tree files
[ ] If there new ways this uses user data that needs to be factored into our Privacy Policy, it has been noted.
Testing:
[ ] Code is clean and well-commented
[ ] Contributor has fully tested the PR manually
[ ] If there are any front-end changes, before/after screenshots are included
[ ] Critical user journeys are covered by Gherkin stories
[ ] Any new interactions have been added to the QA Sheet
[ ] Critical and brittle code paths are covered by unit tests
Summary
Description of the change(s) you made
Removes use of set-output in line with https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Follows Kolibri's use of the pre-commit lite action for committing unlinted files to PRs and branches https://github.com/learningequality/kolibri/blob/develop/.github/workflows/pre-commit.yml#L55
Manual verification steps performed
Screenshots (if applicable)
Does this introduce any tech-debt items?
Reviewer guidance
How can a reviewer test these changes?
Are there any risky areas that deserve extra testing?
References
Comments
Contributor's Checklist
PR process:
CHANGELOGlabel been added to this PR. Note: items with this label will be added to the CHANGELOG at a later timedocslabel has been added if this introduces a change that needs to be updated in the user docs?requirements.txtfiles also included in this PRStudio-specifc:
notranslateclass been added to elements that shouldn't be translated by Google Chrome's automatic translation feature (e.g. icons, user-generated text)pages,components, andlayoutsdirectories as described in the docsTesting:
Reviewer's Checklist
This section is for reviewers to fill out.
yarnandpip)