Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[#2285] Update Github Actions for publish-RepoSense preview #2295

Open
wants to merge 75 commits into
base: master
Choose a base branch
from

Conversation

CYX22222003
Copy link
Contributor

@CYX22222003 CYX22222003 commented Feb 14, 2025

Fix #2285

Proposed commit message

Add additional CI checks for publish-RepoSense

publish-RepoSense is our default tool for deploying RepoSense
reports. It would be good to automate the testing of deployments via
this tool before each merge to strengthen our CI/CD processes.

Let's add a script to audit the preview website.

Other information

@github-actions github-actions bot requested a deployment to dashboard-2295 February 14, 2025 02:36 Abandoned
@github-actions github-actions bot requested a deployment to docs-2295 February 14, 2025 02:36 Abandoned
@CYX22222003 CYX22222003 changed the title Update Github Actions publish preview [#2285] Update Github Actions publish preview Feb 14, 2025
@github-actions github-actions bot requested a deployment to dashboard-2295 February 14, 2025 02:38 Abandoned
@github-actions github-actions bot requested a deployment to docs-2295 February 14, 2025 02:38 Abandoned
@github-actions github-actions bot requested a deployment to dashboard-2295 February 15, 2025 07:50 Abandoned
@github-actions github-actions bot requested a deployment to docs-2295 February 15, 2025 07:50 Abandoned
@github-actions github-actions bot requested a deployment to dashboard-2295 February 16, 2025 00:20 Abandoned
@github-actions github-actions bot requested a deployment to docs-2295 February 16, 2025 00:20 Abandoned
@github-actions github-actions bot requested a deployment to dashboard-2295 February 16, 2025 00:37 Abandoned
@github-actions github-actions bot requested a deployment to docs-2295 February 16, 2025 00:37 Abandoned
@github-actions github-actions bot requested a deployment to dashboard-2295 February 16, 2025 01:21 Abandoned
@github-actions github-actions bot requested a deployment to docs-2295 February 16, 2025 01:21 Abandoned
@github-actions github-actions bot requested a deployment to dashboard-2295 February 16, 2025 01:29 Abandoned
@github-actions github-actions bot requested a deployment to docs-2295 February 16, 2025 01:29 Abandoned
@github-actions github-actions bot requested a deployment to dashboard-2295 February 16, 2025 01:46 Abandoned
@github-actions github-actions bot requested a deployment to docs-2295 February 16, 2025 01:46 Abandoned
@github-actions github-actions bot requested a deployment to dashboard-2295 February 16, 2025 01:50 Abandoned
@github-actions github-actions bot requested a deployment to dashboard-2295 March 6, 2025 11:42 Abandoned
@github-actions github-actions bot requested a deployment to docs-2295 March 6, 2025 11:42 Abandoned
@github-actions github-actions bot requested a deployment to dashboard-2295 March 6, 2025 12:35 Abandoned
@github-actions github-actions bot requested a deployment to docs-2295 March 6, 2025 12:35 Abandoned
@CYX22222003
Copy link
Contributor Author

@sopa301 I have come up with two possible solutions. One is to trigger the CI test by providing the PR number, another one is to trigger after every PR created.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a-DevOps github_actions Pull requests that update GitHub Actions code s.ToReview
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implement a way to test publish-RepoSense deployment pipeline
2 participants