Skip to content

Commit db54e56

Browse files
authored
Update CONTRIBUTING.md
1 parent 2f16a9b commit db54e56

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

CONTRIBUTING.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -52,30 +52,30 @@ We often request you to make some changes to your pull request.
5252
Don't create a new pull request right away if your original submission has issues.
5353
It's much easier for us if you update your original pull request instead.
5454

55-
After you create a pull request, our @csl-bot will first automatically run a number of tests to check whether your style validates and follows our style requirements.
55+
After you create a pull request, our [@csl-bot](https://github.com/csl-bot) will first automatically run a number of tests to check whether your style validates and follows our style requirements.
5656
These tests usually finish within a few minutes.
57-
If there are problems, @csl-bot will give a link to the test report, which contains the identified errors.
57+
If there are problems, [@csl-bot](https://github.com/csl-bot) will leave a comment with the identified errors.
5858
If you have trouble understanding these errors, please post a comment in the pull request and ask for help.
5959

60-
We also have a handful of volunteers who review pull requests, usually within a day or two.
60+
We also have a handful of volunteers who review pull requests, usually within a week or two.
6161

6262
To update your pull request:
6363

6464
1. Visit the "Files changed" tab of your pull request.
65-
2. Click the edit (pencil) icon at the top-right of your style.
65+
2. Click the ellipsis button at the top-right of your style, and select "Edit file" in the ellipsis menu.
6666
3. Make your changes, and click the "Commit changes" button.
6767

6868
Any changes made this way will automatically appear in the pull request, and each commit will trigger a new test report.
6969

7070
Once we are satisfied, we will **merge** your pull request.
71-
This can take hours or days, depending on how busy we are, and on how much back and forth is needed to get your style in acceptable shape.
71+
This can take days or weeks, depending on how busy we are, and on how much back and forth is needed to get your style in acceptable shape.
7272

7373
#### 5. Make additional changes after merging
7474

7575
Once a pull request has been merged, it can no longer be used to submit further changes.
7676
So, if you wish to make additional changes, just create a new pull request.
7777

78-
Please always start from the latest version of the style from our repository, because we often perform maintenance on the repository styles.
78+
Please always start from the latest version of the style from our repository, because we may have performed maintenance on your style or accepted corrections from other contributors.
7979

8080
## Asking for help
8181

0 commit comments

Comments
 (0)