470486104/Server
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Workflows - Minor Formatting

Browse Source
This commit is contained in:
Refringe 2024-04-10 19:56:01 -04:00
parent eb57a5e01f
commit dfaed660ed
No known key found for this signature in database
GPG Key ID: 7715B85B4A6306ED
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.gitea/workflows/run-lint.yaml
View File

@ -53,6 +53,6 @@ jobs:
- name: Fix Instructions - name: Fix Instructions
if: failure() && steps.run-tests.outcome == 'failure' if: failure() && steps.run-tests.outcome == 'failure'
run: | run: |
echo -e "Code linting has failed. The linter has been configured to look for coding errors, defects, and questionable patterns. Please look into resolving these errors. The linter may be able to resolve some of these issues automatically. You can launch the automatic fixer by running the following command from within the 'project' directory. Anything not resolved by running this command must be resolved manually.\nnpm run lint:fix\n\n" echo -e "Code linting has failed. The linter has been configured to look for coding errors, defects, and questionable patterns. Please look into resolving these errors. The linter may be able to resolve some of these issues automatically. You can launch the automatic fixer by running the following command from within the 'project' directory. Anything not resolved by running this command must be resolved manually.\n\nnpm run lint:fix\n"
echo -e "Consistency is professionalism.™" echo -e "Consistency is professionalism.™"
shell: bash shell: bash

4
.gitea/workflows/run-style.yaml
View File

@ -53,7 +53,7 @@ jobs:
- name: Fix Instructions - name: Fix Instructions
if: failure() && steps.check-code-style.outcome == 'failure' if: failure() && steps.check-code-style.outcome == 'failure'
run: | run: |
echo -e "The code style check has failed. To fix this, please ensure your code adheres to the project's style guidelines. You can automatically format the project code by running the following command from within the 'project' directory.\nnpm run style:fix\n\n" echo -e "The code style check has failed. To fix this, please ensure your code adheres to the project's style guidelines. You can automatically format the project code by running the following command from within the 'project' directory.\n\nnpm run style:fix\n"
echo -e "To automatically format code on-save in your IDE, please install the recommended VSCode plugins listed within the 'project/Server.code-workspace' file." echo -e "To automatically format code on-save in your IDE, please install the recommended VSCode plugins listed within the 'project/Server.code-workspace' file.\n"
echo -e "Thank you for keeping our house clean. ♥" echo -e "Thank you for keeping our house clean. ♥"
shell: bash shell: bash

2
.gitea/workflows/run-test.yaml
View File

@ -53,6 +53,6 @@ jobs:
- name: Fix Instructions - name: Fix Instructions
if: failure() && steps.run-tests.outcome == 'failure' if: failure() && steps.run-tests.outcome == 'failure'
run: | run: |
echo -e "Automated tests have failed. This could point to an issue with the commited code, or an updated test that has yet to be updated. Please look into resolving these test failures. The testing suite has a GUI to aid in writing tests. You can launch this by running the following command from within the 'project' directory.\nnpm run test:ui\n\n" echo -e "Automated tests have failed. This could point to an issue with the commited code, or an updated test that has yet to be updated. Please look into resolving these test failures. The testing suite has a GUI to aid in writing tests. You can launch this by running the following command from within the 'project' directory.\n\nnpm run test:ui\n"
echo -e "A test written today is a bug prevented tomorrow.™" echo -e "A test written today is a bug prevented tomorrow.™"
shell: bash shell: bash