Skip to content

Commit

Permalink
Merge pull request #92 from creative-commoners/pulls/master/typo
Browse files Browse the repository at this point in the history
MNT Fix typo
  • Loading branch information
GuySartorelli authored Aug 17, 2023
2 parents 4c02430 + 6d82a68 commit 24e425d
Showing 1 changed file with 5 additions and 2 deletions.
7 changes: 5 additions & 2 deletions .github/workflows/js-prs-issue.yml
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ jobs:
with:
title: JS pull-requests
description: |
This is an automatically created issue used to list automatically created
This is an automatically created issue used to list automatically created
javascript pull requests every 3 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
Expand All @@ -33,7 +33,10 @@ jobs:
### Update JS pull-requests:\n
- [List of update JS pull-requests](https://emtek.net.nz/rhino/tables?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 close those PRs and run the steps below in the "Manually creating update JS pull-requests" section below for those relevant modules\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
Expand Down

0 comments on commit 24e425d

Please sign in to comment.