Skip to content

Commit 88859d8

Browse files
authored
Add stub RFC to SUMMARY.md + add step to instructions (rust-lang#1802)
1 parent f306a44 commit 88859d8

File tree

2 files changed

+4
-2
lines changed

2 files changed

+4
-2
lines changed

rfc/src/SUMMARY.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,4 +7,5 @@
77
# Kani RFCs
88

99
- [0001-mir-linker](rfcs/0001-mir-linker.md)
10+
- [0002-function-stubbing](rfcs/0002-function-stubbing.md)
1011

rfc/src/intro.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,9 +34,10 @@ This is the overall workflow for the RFC process:
3434
1. Create an RFC
3535
1. Create a tracking issue for your RFC (e.g.: [Issue-1588](https://github.com/model-checking/kani/issues/1588)).
3636
2. Start from a fork of the Kani repository.
37-
3. Copy the template file ([`rfc/src/template.md`](./template.md)) to `rfc/src/<ID_NUMBER><my-feature>.md`.
37+
3. Copy the template file ([`rfc/src/template.md`](./template.md)) to `rfc/src/rfcs/<ID_NUMBER><my-feature>.md`.
3838
4. Fill in the details according to the template instructions.
39-
5. Submit a pull request.
39+
5. Add a link to the new RFC inside [`rfc/src/SUMMARY.md`](https://github.com/model-checking/kani/blob/main/rfc/src/SUMMARY.md)
40+
6. Submit a pull request.
4041
2. Build consensus and integrate feedback.
4142
1. RFCs should get approved by at least 2 Kani developers.
4243
2. Once the RFC has been approved, update the RFC status and merge the PR.

0 commit comments

Comments
 (0)