Repository navigation
chore/validate-apps - #250
claytonneal wants to merge 2 commits into
Conversation
|
@claytonneal I believe there is a validation in the validate.ts file: https://github.com/vechain/app-hub/blob/master/scripts/validate.ts#L110 |
|
How about make it a scheduled workflow? I will change the script to check all apps then report all errors. |
|
If I am remembering correctly, one app used cloudflare and checkLink reports error but it works at the browser level, maybe that need extra confirm by human. |
script updated #252 |
| with: | ||
| fetch-depth: 0 |
There was a problem hiding this comment.
| with: | |
| fetch-depth: 0 |
validate link does not require full history
| run: npm run validate:links | ||
| env: | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} |
There was a problem hiding this comment.
| run: npm run validate:links | |
| env: | |
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | |
| run: npm run validate:link |
validate link does not need a gh token, PR mode needed
There was a problem hiding this comment.
ok thanks tony!
|
@claytonneal this issue is super cool! Cant want to see it in prod ;) |
|
Add script and workflow to check if apps are returning http 404/500 etc