[#2384] Testing publish-Reposense on every push/PR on the main repo.

[feliciahmq]

Fixes #2384

Proposed commit message

Other information

ive added a trigger-regression-test.yml workflow in RepoSense that automatically triggers a workflow in publish-RepoSense on every pull request. this trigger sends over the PR number and commit SHA to the downstream repo.

in publish-reposense, it clones the RepoSense repository at the specified SHA, builds the project with Gradle, runs the website on a GitHub Actions runner and uses Lighthouse CLI to audit the generated site.

a REPO_DISPATCH_TOKEN needs to be created as it is required when using curl to call repository_dispatch GitHub API in a different repo (publish-reposense).

[CYX22222003]

Hi @feliciahmq, thank you very much for looking into this issue! It is impressive to see the progress you have made.

Could you kindly share the links to the CI/CD actions that you have tested on your forked repos? That will be much easier for us to review and keep track of changes.

Also, I remember there is a specific case where it will cause the blank page to appear, but I forgot the exact details @sopa301 , could you please help clarify that scenario again? It would be great if that case can be tested as well on your forked repo.

[sopa301]

@CYX22222003 Are you referring to #2202? Some details are in #2203, which can be used to derive a test case for this PR

[CYX22222003]

@CYX22222003 Are you referring to #2202? Some details are in #2203, which can be used to derive a test case for this PR

Yes, that's the case i am looking for. Thank you for the help!

[feliciahmq]

https://github.com/feliciahmq/RepoSense/actions/runs/16550460816

• in Trigger publish-RepoSense Test Workflow, you can see the pr and sha sent

https://github.com/feliciahmq/publish-RepoSense/actions/runs/16552028862

• in Log Trigger Info section, you can see the pr and sha extracted

[github-actions]

Hi,
We are going to mark this PR as stale because it has been inactive for the past 30 days.
If no further activity occurs within the following 7 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 7 days and leave a comment to remove the stale label.
Do let us know if you are stuck so that we can help you!'

[github-actions]

Hi,
We are going to mark this PR as stale because it has been inactive for the past 30 days.
If no further activity occurs within the following 7 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 7 days and leave a comment to remove the stale label.
Do let us know if you are stuck so that we can help you!'

[github-actions]

This PR was closed because it has been marked as stale for 7 days with no activity.
Feel free to reopen this PR if you would like to continue working on it.