Skip to content

Fix links in the book sections related to tool application #101

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

Merged
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doc/src/SUMMARY.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@

- [General Rules](./general-rules.md)
- [Challenge Template](./template.md)
- [Tool application](./todo.md)
- [Tool application](./general-rules.md#tool-applications)

- [Verification Tools](./tools.md)
- [Kani](./tools/kani.md)
Expand Down
2 changes: 1 addition & 1 deletion doc/src/general-rules.md
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ Follow the following steps to create a new proposal:

Solutions must be automated using one of the tools previously approved and listed [here](tools.md#approved-tools):

* Any new tool that participants want to enable will require an application using the Issue template [Tool application](todo.md).
* Any new tool that participants want to enable will require an application using the issue template for [tool applications](https://github.com/model-checking/verify-rust-std/blob/main/.github/TOOL_REQUEST_TEMPLATE.md).
* The tool will be analyzed by an independent committee consisting of members from the Rust open-source developers and AWS
* A new tool application should clearly specify the differences to existing techniques and provide sufficient background
of why this is needed.
Expand Down
Loading