Skip to content

[docs]: invalid reference in Running the setup in CI section #2621

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

Closed
1 task done
Konippi opened this issue Mar 26, 2025 · 2 comments · Fixed by keploy/docs#503
Closed
1 task done

[docs]: invalid reference in Running the setup in CI section #2621

Konippi opened this issue Mar 26, 2025 · 2 comments · Fixed by keploy/docs#503
Labels
docs Documentation Improvements or additions to documentation

Comments

@Konippi
Copy link

Konippi commented Mar 26, 2025

👀 Is there an existing issue for this?

  • I have searched and didn't find similar issue

💭 Description

There is an invalid reference in the "Running the setup in CI" section.
The target URL points to: https://github.com/keploy/keploy/blob/main/.github/workflows/build_stage.yml.

However, this workflow has already been deleted in PR #2272.

💻 Repository

docs

@Konippi Konippi added the Documentation Improvements or additions to documentation label Mar 26, 2025
@github-actions github-actions bot added the docs label Mar 26, 2025
@sagar2395
Copy link

Looks like linked PR workflow run is failing due to Vale linter. Can I take this up as this is unassigned currently ??

@khareyash05
Copy link
Contributor

khareyash05 commented Apr 27, 2025

Looks like linked PR workflow run is failing due to Vale linter. Can I take this up as this is unassigned currently ??

Hey @sagar2395 , i guess this PR was on our backlog, we had to merge as it was complete. But it seems the pipelines are failing from quite a while now, you can take up the issue, #2696

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants