Enable artifacts creation at pull request

[igorpecovnik]

Description

One of the long missing important feature at the pull request stage is pre-merge build test. Of any artifact. This implement a call to use our standard build-all-artifacts action script with additional parameters: we need to attach build framework to PR commit ID and tell script that we don’t need to upload or download artifacts to / from ORAS cache. For security reasons, this will be done separately.

Build script will run only when comment /build is added to the PR by Armbian organisation member that is part of "Release manager" team.

Jira reference number AR-1886

How Has This Been Tested?

• PR executes actions
• When PR is updated, active workflow is canceled, new starts
• Artifacts are not pushed to ORAS cache

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

[viraniac]

I am curious about the change in linux-sunxi-edge.config, was that done for testing purpose or is it required for something?

[igorpecovnik]

was that done for testing purpose

this.

[igorpecovnik]

/build

[igorpecovnik]

/rebase

[igorpecovnik]

/build

[igorpecovnik]

/build