Action to build js files automatically

[da-h]

Description

This PR moves the requirement to commit build files from the contributor to a dedicated github action.

Motivation and Context

The goal of this PR is to ensure consistency across builds on the one hand, and to increase security of the deployment on the other hand.

How Has This Been Tested?

See the action result in my own test branch

Notes

The new action triggers on any pushes of the js/** files. Alternatively, it would be reasonable to either

• trigger on pushes onto master only
• trigger on closing of merge requests (I see no direct possibility to trigger on "merged" merge requests)

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• [ ] My code follows the code style of this project.
• [ ] My change requires a change to the documentation.
• [x] I have updated the documentation accordingly.
• [ ] For JavaScript changes, I have re-generated the minified JavaScript code.

[da-h]

Quick question on the suggestion for improvement: what do you mean exactly? Only resource I can find is the use of ${{ failure() }} in an action to save build failure logs. I am somewhat at a loss here. :sweat_smile:

[JackUrb]

To some degree I'm not sure if it would already happen (that the action would display a failure) if you were to make a mistake. Can be tested by putting a package that doesn't exist into the package.json (to test npm install) and then making an unparsable syntax error in the js code (to test npm run build).

[da-h]

Indeed, this is the case. I just double checked this for both mentioned scenarios: