-
Notifications
You must be signed in to change notification settings - Fork 1
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
Testing link-checker-gpt 0.1.0-beta #13
Conversation
Signed-off-by: Kingdon Barrett <[email protected]>
3b40e14
to
2a43434
Compare
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Dockerize
Let's give it a configurable URL, configure it to check for a healthy sitemap and configurable timeout We can clarify in the README how to adopt it in your repo, what options it has, and test it in a repository for some other domain. Those things shouldn't be very difficult to add. https://developer.fermyon.com/bartholomew/seo#generating-a-sitemap (We have one of these blogs and we can add a sitemap to it to make it work with this, it's recommended anyway and I haven't done it yet...) |
Move the workflow to root directory, following: https://docs.github.com/en/actions/creating-actions/about-custom-actions#good-practices-for-release-management Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
preserve it for posterity in a separate .yml Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
but we can tell it to try again and keep polling until timeout or the PREVIEW_URL site becomes ready. Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
the advice to use env is for scripts that users embed in their own repos https://docs.github.com/en/actions/using-workflows/using-github-cli-in-workflows we need to take githubToken as an input, evidently Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
not sure which of these or if both are effective, but let's see if this breaks anything (it ought not!) Signed-off-by: Kingdon Barrett <[email protected]>
The |
I will close |
Signed-off-by: Kingdon Barrett <[email protected]>
Fix #15
Unsure if we can use v0 prerelease versioning for a GitHub action.
May just promote v1 if everything seems to be working. Still need to finish testing:
There needs to be a PR so we can see the test workflow executing.
It will still fail, because we are waiting for this one and its friends to merge: