Skip to content
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

JS pull-requests #122

Closed
github-actions bot opened this issue Oct 1, 2023 · 2 comments
Closed

JS pull-requests #122

github-actions bot opened this issue Oct 1, 2023 · 2 comments

Comments

@github-actions
Copy link

github-actions bot commented Oct 1, 2023

This is an automatically created issue used to list automatically created javascript pull requests every 3 months.

It was created by the .github/workflows/js-prs-issue.yml workflow in the silverstripe/.github repository.

Triage instructions (Silverstripe Ltd CMS Squad)

  1. Put on the following labels:
    • type/enhancement
    • impact/low
    • affects/v5
  2. Move this issue to the "Ready" column on our internal zenhub board

Update JS pull-requests:

  • List of update JS pull-requests
  • Merge these PRs if there are no merge-conflicts
  • 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:

  1. Ensure you have the default branch checked out for the module you are updating e.g. 5
  2. Ensure silverstripe/silverstripe-admin is installed in a sibling directory
  3. In the silverstripe-admin directory, ensure the default branch is checked out e.g. 2
  4. In the silverstripe-admin directory, run yarn install
  5. In the directory of module you're updating JS for, run yarn upgrade
  6. Run yarn build in the directory of module you're updating JS for
  7. Git commit, push the changes and create a pull-request
  8. List the pull-request(s) on this issue
  9. Move this issue to the peer review column on the CMS Squad internal zenhub board

Dependabot pull-requests:

  • List of dependabot pull-requests
  • Most of these should be automatically closed if the "Update JS pull-requests" above are merged
  • You can make a judgement call as to whether to merge any easy ones that are left

Not going to fix the following failures because they're unsupported and non-trivial

PRs

@emteknetnz
Copy link
Member

@GuySartorelli re the ckan - would it make sense to remove the upgrade-js workflow from that module since it's unsupported?

@GuySartorelli
Copy link
Member

Good idea. Done in silverstripe/silverstripe-ckan-registry#298

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants