-
Notifications
You must be signed in to change notification settings - Fork 4
/
Copy pathauthorreview.Rmd
18 lines (12 loc) · 1.27 KB
/
authorreview.Rmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
# Respond to Feedback {#respond}
```{block, type='summaryblock', echo=TRUE}
This chapter outlines how an author of a blog post or tech note can find and respond to comments from an editor in the GitHub pull request review interface.
```
Once you have [submitted](#submitpost) your blog post or tech note, an editor will review your post providing comments on both [content](#content) (is the narrative clear?) and [technical](#technical) (does it follow our Style Guide?) aspects.
Browse [Chapter 5.1 Review a post](#review) to see how editors use the [GitHub web interface](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests) to suggest edits, make comments, and approve or request changes to your pull request.
To respond to an editor's review:
- Respond to every inline comment with a thumbs up or thumbs down emoji so the editor knows you have seen it.
- It's ok to explain why you disagree with some comments.
- [_Resolve conversation_](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#resolving-conversations) for items you have addressed.
- Tag the editor when you have finished addressing their comments.
The editor will confirm when your post is ready for publication.