![Wartune hall of heroes server release](https://loka.nahovitsyn.com/216.jpg)
![board for github board for github](https://justinfincher.github.io/BoardForGitHub-Landing/img/feature-6.png)
Work is underway on this issue or pull request. Tickets in this column need to have an assignee.
![board for github board for github](https://github.blog/wp-content/uploads/2018/06/41678742-ccad1f28-7480-11e8-8d80-3fa0806414de.gif)
Work that the GitHub has triaged, but hasn't started working on yet. Move the ticket to the appropriate column.Give the ticket an assignee (most likely you).Indicates which New Relic product group is associated with this issue. Use from_tw when it's created by a docs writer, from_internal when it's created by a Relic, and from_external when it's from outside the company. Use this label to indicate who created the issue or pull request.
#BOARD FOR GITHUB CODE#
Use this label to indicate an issue or pull request relates to content (versus the code of the site).
#BOARD FOR GITHUB ARCHIVE#
If it's an eng issue or pull request, you can just Archive it to remove it from the board. Determine if the pull request or issue is content-related.New issues and pull requests flow into this column automatically. Move any ready-for-review pull requests into the correct column. The Hero should look at this column multiple times per day in case a pull request has been marked ready for review. Do not "hold" pull requests or issues here. This column should only be for draft pull requests. Do not merge until their owner moves them out of the column. These issues and pull requests are in a draft state. If you're reviewing a pull request from a fellow docs writer, add your comments and mark the pull request as Approved, then move it to Waiting on TW to merge. If it's a pull request from outside the docs team, the reviewer is also responsible for merging the pull request into develop. Reviewer means you are actively reviewing a pull request.If you are no longer owning a given pull request or issue, take your name off as assignee. Assignee means you own the pull request or issue and are getting it into a merge-ready state.A note on Assignee vs ReviewerĪssignee and Reviewer have different meanings: The board is divided into a series of columns so we can see visually what the status of each issue and pull request is. The Docs pull requests and Issues board is our source of truth for what's going on in our project.
![Wartune hall of heroes server release](https://loka.nahovitsyn.com/216.jpg)