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

External Link Check Report - Sunday, 7. Jul 2024 #282

Closed
github-actions bot opened this issue Jul 7, 2024 · 1 comment
Closed

External Link Check Report - Sunday, 7. Jul 2024 #282

github-actions bot opened this issue Jul 7, 2024 · 1 comment

Comments

@github-actions
Copy link

github-actions bot commented Jul 7, 2024

Summary

Status Count
πŸ” Total 1507
βœ… Successful 999
⏳ Timeouts 3
πŸ”€ Redirected 0
πŸ‘» Excluded 353
❓ Unknown 7
🚫 Errors 145

Errors per input

Errors in content/blog/simulating-cloudevents-with-asyncapi.md

Errors in content/blog/microcks-on-kind.md

Errors in content/events/DevoxxFR2023.md

Errors in content/blog/microcks-1.9.0-release.md

Errors in content/blog/microcks-1.1.0-release.md

Errors in content/blog/microcks-on-minikube.md

Errors in content/blog/microcks-hub-announcement.md

Errors in content/documentation/administrating/users.md

Errors in content/blog/docker-desktop-extension-0.2.md

Errors in content/blog/install-microcks-on-aws.md

Errors in content/blog/microcks-1.7.0-release.md

Errors in content/documentation/automating/github-actions.md

Errors in content/blog/observability-for-microcks-at-scale.md

Errors in content/events/PastArchive.md

Errors in content/blog/async-features-with-docker-compose.md

Errors in content/blog/docker-desktop-extension-launch.md

Errors in content/blog/mocking-oidc-redirect.md

Errors in content/blog/microcks-1.6.0-release.md

Errors in content/documentation/installing/docker-compose.md

Errors in content/blog/advanced-dispatching-constraints.md

Errors in content/blog/graphql-features-what-to-expect.md

Errors in content/blog/microcks-1.0.0-release.md

Errors in content/blog/microcks-1.5.0-release.md

Errors in content/documentation/using/graphql.md

Errors in content/blog/microcks-1.4.1-release.md

Errors in content/blog/continuous-testing-all-your-apis.md

Errors in content/blog/microcks-1.7.1-release.md

Errors in content/blog/microcks-1.3.0-release.md

Errors in content/documentation/installing/podman-compose.md

Errors in content/documentation/using/metadata.md

Errors in content/documentation/using/asyncapi.md

Errors in content/blog/microcks-0.9.0-release.md

Errors in content/blog/extend-microcks-with-custom-libs.md

Errors in content/documentation/using/grpc.md

Errors in content/blog/microcks-1.5.2-release.md

Errors in content/documentation/using/openapi.md

Errors in themes/microcks/layouts/career/single.html

Errors in content/blog/microcks-1.2.0-release.md

Errors in content/blog/apache-kafka-mocking-testing.md

Errors in content/blog/microcks-1.9.1-release.md

Errors in content/blog/microcks-1.5.1-release.md

Errors in content/blog/microcks-1.8.0-release.md

Errors in content/documentation/using/postman.md

Errors in content/blog/jb-hunt-mock-it-till-you-make-it.md

Errors in content/blog/microcks-1.8.1-release.md

Errors in content/documentation/installing/deployment-options.md

Copy link
Author

github-actions bot commented Jul 7, 2024

🌟 Join Us in Keeping Our Website Up-to-Date and Error-Free! πŸš€

Dear Community Members,

We're on a mission to maintain our website, microcks.io, in top-notch condition, ensuring that it remains a valuable resource for everyone. To achieve this goal, we need your help!

Why Contribute?

  • Ensure Quality: By collectively maintaining the website, we can promptly address broken links and outdated content, ensuring a seamless browsing experience for all visitors.

  • Stay Relevant: Regular updates keep our content fresh and relevant, reflecting the latest developments in our field.

  • Community Engagement: Contributing allows you to be an active part of our community, sharing and collaborating with fellow enthusiasts.

How to Contribute?

  • One PR Per File: For ease of collaboration and review, please create one pull request per corrected file.

  • Tag Issue Number: Always tag the issue number (#??) in your pull request description to associate it with the relevant issue.

  • Verify Links: If you encounter rate limit errors for LinkedIn or GitHub profiles, click on the link, verify its accuracy, and update the .lycheeignore file accordingly to prevent future error reporting.

Let's work together to maintain the excellence of our website! Your contributions make a real difference. 🌟

Happy Contributing! πŸŽ‰

Warm Regards,
Yacine

@yada yada closed this as completed Jul 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant