Action allowing us to publish backported changes

[witmicko]

We're using hardcoded build source references and target versions to ensure we have clear control over what gets deployed where. This action is tailored to only create pull requests against the gh-pages branch.

example action run:
https://github.com/witmicko/phishing-warning/actions/runs/7033539537
it builds and commits changes to gh-pages-backport branch, I then manually created this PR
witmicko#1

[Gudahtt]

Rather than checking out this branch as a sub path, have you considered using the same github-actions deploy action we use elsewhere?

phishing-warning/.github/workflows/publish-gh-pages.yml

Line 32 in 0f562ba

uses: peaceiris/actions-gh-pages@068dc23d9710f1ba62e86896f84735d869951305

We can use a matrix to iterate over each version target as well

[witmicko]

tried this first but actions were failing when it ran them, will revisit this later tough as it is more elegant solution

[Gudahtt]

Is this meant as an alternative to #81 ?

Grouping by major did seem like a nicer way of handling this going forward

[witmicko]

Is this meant as an alternative to #81 ?

Grouping by major did seem like a nicer way of handling this going forward

no, not alternative, just stop-gap for this backport, Im also in favour of #81

[NicholasEllul]

Looks good as a temporary backport action 👍 Noting for context that this is here to facilitate backporting bug fixes until something like #81 can be incorporated.

Update: i see this was already noted above

[NicholasEllul]

Did we hardcode this to prevent others from using it incorrectly and requiring a review for each change?

[witmicko]

yes, also not using inputs as they can have mistakes and are harder to check

[Gudahtt]

LGTM!