JS PRs issue #7
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| name: JS PRs issue | |
| on: | |
| # At 12:00 on day-of-month 1 in March and September. | |
| # This is 12 hours after update-js workflows run on repos such as silverstripe/asset-admin | |
| schedule: | |
| - cron: '0 12 1 3,9 *' | |
| workflow_dispatch: | |
| permissions: {} | |
| jobs: | |
| js-prs-issue: | |
| name: JS PRs issue | |
| # Only run cron on the silverstripe account | |
| if: (github.event_name == 'schedule' && github.repository_owner == 'silverstripe') || (github.event_name != 'schedule') | |
| runs-on: ubuntu-latest | |
| permissions: | |
| issues: write | |
| steps: | |
| - name: JS PRs issue | |
| uses: silverstripe/gha-issue@v1 | |
| with: | |
| title: JS pull-requests | |
| description: | | |
| This is an automatically created issue used to list automatically created | |
| javascript pull requests every 6 months.\n | |
| \n | |
| It was created by the `.github/workflows/js-prs-issue.yml` workflow in the [silverstripe/.github](https://github.com/silverstripe/.github/) repository.\n | |
| \n | |
| ### Triage instructions (Silverstripe Ltd CMS Squad)\n | |
| 1. Put on the following labels:\n | |
| - `type/enhancement`\n | |
| - `impact/low`\n | |
| - `affects/v5`\n | |
| 2. Move this issue to the "Ready" column on our internal zenhub board\n | |
| \n | |
| ### Update JS pull-requests:\n | |
| - [List of update JS pull-requests](https://rhino.silverstripe.org/?t=open-prs&filters={%22title%22%3A%22DEP%20Update%20JS%20dependencies%22})\n | |
| - Merge these PRs if there are no merge-conflicts\n | |
| - 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\n | |
| \n | |
| ### Manually creating update JS pull-requests:\n | |
| 1. Ensure you have the default branch checked out for the module you are updating e.g. `5`\n | |
| 2. Ensure `silverstripe/silverstripe-admin` is installed in a *sibling* directory\n | |
| 3. In the `silverstripe-admin` directory, ensure the default branch is checked out e.g. `2`\n | |
| 4. In the `silverstripe-admin` directory, run `yarn install`\n | |
| 5. In the directory of module you're updating JS for, run `yarn upgrade`\n | |
| 6. Run `yarn build` in the directory of module you're updating JS for\n | |
| 7. Git commit, push the changes and create a pull-request\n | |
| 8. List the pull-request(s) on this issue\n | |
| 9. Move this issue to the peer review column on the CMS Squad internal zenhub board\n |