Skip to content

Actions: Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines

Actions

RST Preview Comment

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
rst-preview-comment.yml
1,679 workflow runs
1,679 workflow runs

Filter by Event

⌥ + click/return to exclude

Filter by Status

⌥ + click/return to exclude

Filter by Branch

⌥ + click/return to exclude

Filter by Actor

⌥ + click/return to exclude
[Automation] Modify workflow to, instead of PR, add comment with ReStructured Text RST Preview Comment #29: Issue #224 edited by PLeVasseur
1s
1s
[Coding Guideline]: Do Not Depend on Function Pointer Identity Across Crates RST Preview Comment #28: Issue #255 edited by PLeVasseur
27s
27s
[Coding Guideline]: Do Not Depend on Function Pointer Identity Across Crates RST Preview Comment #27: Issue #255 edited by PLeVasseur
19s
19s
Exception(s) portion of Coding Guideline issue template not propagated to guideline in RST RST Preview Comment #26: Issue #261 opened by PLeVasseur
1s
1s
[Coding Guideline]: Do Not Depend on Function Pointer Identity Across Crates RST Preview Comment #25: Issue #255 edited by PLeVasseur
20s
20s
[Coding Guideline]: Do Not Depend on Function Pointer Identity Across Crates RST Preview Comment #24: Issue #255 edited by PLeVasseur
25s
25s
[Coding Guideline in RST]: Do not perform ordering comparisons on pointers from different allocations RST Preview Comment #23: Issue #259 opened by rcseacord
1s
1s
[Coding Guideline]: Do Not Depend on Function Pointer Identity Across Crates RST Preview Comment #22: Issue #255 edited by PLeVasseur
23s
23s
[Coding Guideline]: Do Not Depend on Function Pointer Identity Across Crates RST Preview Comment #21: Issue #255 edited by PLeVasseur
18s
18s
UCG - Rust's Unsafe Code Guidelines RST Preview Comment #20: Issue #257 opened by rcseacord
1s
1s
[Coding Guideline]: Do Not Depend on Function Pointer Identity Across Crates RST Preview Comment #19: Issue #255 edited by rcseacord
27s
27s
[Coding Guideline]: Do not compare raw pointers to allocations with different provenance RST Preview Comment #18: Issue #246 edited by rcseacord
30s
30s
[Coding Guideline]: Do not compare raw pointers to allocations with different provenance RST Preview Comment #17: Issue #246 edited by rcseacord
33s
33s
[Coding Guideline]: Do not compare raw pointers to allocations with different provenance RST Preview Comment #16: Issue #246 edited by rcseacord
25s
25s
[Coding Guideline]: Do not compare raw pointers to allocations with different provenance RST Preview Comment #15: Issue #246 edited by rcseacord
24s
24s
[Coding Guideline]: Do Not Depend on Function Pointer Identity Across Crates RST Preview Comment #14: Issue #255 opened by rcseacord
24s
24s
Rust Safety Coding Guidelines (Advanced / Subtle Pitfalls) RST Preview Comment #13: Issue #254 opened by rcseacord
1s
1s
[Coding Guideline]: Do not create values from uninitialized memory / dummy to test RST RST Preview Comment #12: Issue #248 edited by PLeVasseur
22s
22s
[Coding Guideline]: Do not create values from uninitialized memory / dummy to test RST RST Preview Comment #11: Issue #248 edited by PLeVasseur
34s
34s
[Coding Guideline]: Assure visibility of unsafe tokens in unsafe code RST Preview Comment #10: Issue #252 edited by workingjubilee
31s
31s
[Coding Guideline]: Assure visibility of unsafe tokens in unsafe code RST Preview Comment #9: Issue #252 edited by workingjubilee
21s
21s
[Coding Guideline]: Assure visibility of unsafe tokens in unsafe code RST Preview Comment #8: Issue #252 opened by workingjubilee
20s
20s
[Coding Guideline]: Do not compare raw pointers to allocations with different provenance RST Preview Comment #7: Issue #246 edited by rcseacord
18s
18s
[Coding Guideline]: Do not compare raw pointers to allocations with different provenance RST Preview Comment #6: Issue #246 edited by rcseacord
20s
20s
[Coding Guideline]: Do not create values from uninitialized memory / dummy to test RST RST Preview Comment #5: Issue #248 edited by PLeVasseur
29s
29s
ProTip! You can narrow down the results and go further in time using created:<2025-12-05 or the other filters available.