Petr Tsvetkov
commited on
Commit
•
b681eac
1
Parent(s):
221db9e
fix the help text
Browse files- survey_guide.md +7 -6
survey_guide.md
CHANGED
@@ -1,10 +1,10 @@
|
|
1 |
**Thank you for agreeing to take part!**
|
2 |
|
3 |
In this study, we study how developers interact with
|
4 |
-
commit message text generated by
|
5 |
-
that you are in
|
6 |
commit message (the changes to the code are shown on the
|
7 |
-
left). You have generated a message using
|
8 |
You can see this generated message on the top right.
|
9 |
However, the message will not necessarily be perfect!
|
10 |
|
@@ -12,8 +12,9 @@ Now, _you need to edit the commit message_ so that it is good enough
|
|
12 |
to publish to VCS. Please do this directly in the text
|
13 |
box. When you're done, press the "Submit" button: you
|
14 |
will proceed to the next commit and the next generated
|
15 |
-
message. Please
|
16 |
-
as you can.
|
|
|
17 |
|
18 |
During the study, we collect all keystrokes made _in a
|
19 |
-
text window_, as well as the resulting message
|
|
|
1 |
**Thank you for agreeing to take part!**
|
2 |
|
3 |
In this study, we study how developers interact with
|
4 |
+
commit message text generated by a LLM. Imagine
|
5 |
+
that you are in the IDE and writing a
|
6 |
commit message (the changes to the code are shown on the
|
7 |
+
left). You have generated a message using a LLM.
|
8 |
You can see this generated message on the top right.
|
9 |
However, the message will not necessarily be perfect!
|
10 |
|
|
|
12 |
to publish to VCS. Please do this directly in the text
|
13 |
box. When you're done, press the "Submit" button: you
|
14 |
will proceed to the next commit and the next generated
|
15 |
+
message. Please repeat the process for as many commits
|
16 |
+
as you can. If you are stuck on some commit, feel free to skip it
|
17 |
+
using the button on the top right.
|
18 |
|
19 |
During the study, we collect all keystrokes made _in a
|
20 |
+
text window_, as well as the resulting message.
|