You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there are merge conflicts in some PRs, then manually run the "Update JS" github action in the affected module. The github action will automatically close the old PR and delete the old branch.- If the new PRs still have merge conflicts, then close those PRs and run the steps below in the "Manually creating update JS pull-requests" section below for those relevant modules
Manually creating update JS pull-requests:
Ensure you have the default branch checked out for the module you are updating e.g. 5
Ensure silverstripe/silverstripe-admin is installed in a sibling directory
In the silverstripe-admin directory, ensure the default branch is checked out e.g. 2
In the silverstripe-admin directory, run yarn install
In the directory of module you're updating JS for, run yarn upgrade
Run yarn build in the directory of module you're updating JS for
Git commit, push the changes and create a pull-request
List the pull-request(s) on this issue
Move this issue to the peer review column on the CMS Squad internal zenhub board
This is an automatically created issue used to list automatically created javascript pull requests every 6 months.
It was created by the
.github/workflows/js-prs-issue.yml
workflow in the silverstripe/.github repository.Triage instructions (Silverstripe Ltd CMS Squad)
type/enhancement
impact/low
affects/v5
Update JS pull-requests:
Manually creating update JS pull-requests:
5
silverstripe/silverstripe-admin
is installed in a sibling directorysilverstripe-admin
directory, ensure the default branch is checked out e.g.2
silverstripe-admin
directory, runyarn install
yarn upgrade
yarn build
in the directory of module you're updating JS forPRs
The text was updated successfully, but these errors were encountered: