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
When a repo's data is retrieved, it should include records of code reviews:
Code Reviews including date/time it was submitted, id # for the associated PR, reviewer (username), status [comment, approve, or request changes], description.
When exporting, the value in the CSV's Action column should be code_review and the Author column should be the person who submitted the code review.
The text was updated successfully, but these errors were encountered:
Yes, put all new work on a dedicated feature branch. When it's ready for production, create a pull request and the rest of us will verify and review it.
@kbuffardi , added the code on "code-review-feature" branch and created a pull request. I find the code reviews are being captured and the code review details are being exported to the .csv file as well.
When a repo's data is retrieved, it should include records of code reviews:
Action
column should becode_review
and theAuthor
column should be the person who submitted the code review.The text was updated successfully, but these errors were encountered: