build testing

[ranjinimn]

Trying to test the build workflow.

[ranjinimn]

@hardys This is in continuation with the conversation we had about the replacement for the daps script that Andrew Garcey had created.
I worked with my team and he guided me to complete this.
Please let me know if you have any questions. If we are good to go, please approve, and then I will merge this PR.

[ranjinimn]

@hardys Now the PR is ready for review. Please let me know if you have any questions.

[hardys]

Thanks a lot for the work on this! I have two questions:

• How can we replace the preview currently published at https://suse-edge.github.io/ (this PR removes the workflow to update it, can we either reinstate it, or propose an alternative approach?)
• Is it possible to update the local build instructions to align with this new workflow? https://github.com/suse-edge/suse-edge.github.io?tab=readme-ov-file#how-to-testbuild-locally

[ranjinimn]

Thanks a lot for the work on this! I have two questions:

• How can we replace the preview currently published at https://suse-edge.github.io/ (this PR removes the workflow to update it, can we either reinstate it, or propose an alternative approach?)
• Is it possible to update the local build instructions to align with this new workflow? https://github.com/suse-edge/suse-edge.github.io?tab=readme-ov-file#how-to-testbuild-locally

@hardys Thank you for the feedback. I have edited the script to publish on https://suse-edge.github.io/. Once the PR is merged, we will need to monitor to check if it gets published there.
Regarding the local build, it is already documented in https://github.com/suse-edge/suse-edge.github.io/tree/main/asciidoc#building-the-suse-branded-version-locally. I can remove the content in the present file and add the link to remove obsolete information.

[hardys]

Previously we had two distinct workflows:

• test-deploy which runs only on pull_request, to verify the PR can build without errors
• deploy which runs only on push (e.g when a PR merges) so the updated branch can be rebuilt and pushed to GH pages

If I'm reading this change correctly we now have both workflows combined, and running in both scenarios which I don't think is correct (we'll publish even for a PR before merging?)

I think we should likely keep the previous structure with two workflows, but adjust the workflow contents to align with this new file?

[ranjinimn]

Yes, correct. We had 2 defined workflows. Thank you for the suggestion :) I will separate the 2 actions and see if that helps in aligning the new workflow with the old one.