You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/tools/rust-analyzer/CONTRIBUTING.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,8 @@
1
+
> [!IMPORTANT]
2
+
> We have enacted a feature freeze for IDE assists to cope with the PR backlog as well as allowing us to prepare for the rowan transition!
3
+
> If you submit a PR that **adds** new ide-assists, chances are very high that we will just close it on this basis alone until we have the capacity to deal with them again.
4
+
5
+
1
6
# Contributing to rust-analyzer
2
7
3
8
Thank you for your interest in contributing to rust-analyzer! There are many ways to contribute
@@ -28,3 +33,11 @@ possibility of someone putting a lot of work into a feature that is then going t
28
33
it out of scope (be it due to generally not fitting in with rust-analyzer, or just not having the
29
34
maintenance capacity). If there already is a feature issue open but it is not clear whether it is
30
35
considered accepted feel free to just drop a comment and ask!
36
+
37
+
## Use of AI tools
38
+
39
+
AI tool use is not discouraged on the rust-analyzer codebase, as long as it meets our quality standards.
40
+
We kindly ask you to disclose usage of AI tools in your contributions.
41
+
If you used them without disclosing it, we may reject your contribution on that basis alone due to the assumption that you likely not reviewed your own submission (so why should we?).
42
+
43
+
We may still reject AI-assisted contributions if we deem the quality of the contribution to be unsatisfactory as to reduce impact on the team's review budget.
0 commit comments