Skip to content

Commit 0aa2ba1

Browse files
authoredMay 7, 2021
fix: improve text in comment (#367)
1 parent 3b1edd6 commit 0aa2ba1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed
 

‎lib/get-fail-comment.js

+3-3
Original file line numberDiff line numberDiff line change
@@ -19,17 +19,17 @@ module.exports = (branch, errors) => `## :rotating_light: The automated release
1919
branch.name
2020
}\` branch failed. :rotating_light:
2121
22-
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
22+
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
2323
24-
You can find below the list of errors reported by **semantic-release**. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
24+
You can find below the list of errors reported by **semantic-release**. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
2525
2626
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
2727
2828
Once all the errors are resolved, **semantic-release** will release your package the next time you push a commit to the \`${
2929
branch.name
3030
}\` branch. You can also manually restart the failed CI job that runs **semantic-release**.
3131
32-
If you are not sure how to resolve this, here is some links that can help you:
32+
If you are not sure how to resolve this, here are some links that can help you:
3333
- [Usage documentation](${USAGE_DOC_URL})
3434
- [Frequently Asked Questions](${FAQ_URL})
3535
- [Support channels](${GET_HELP_URL})

0 commit comments

Comments
 (0)