-
Notifications
You must be signed in to change notification settings - Fork 1
Keh 735 add team info #54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Would you be able to merge master into this branch @mwirikia so that the data_logger is using the most up to date version as the format of copilot_teams changed to enable KEH-1122? This is referring to the lambda_data_logger/main.py line 68. Thank you 😃 |
TotalDwarf03
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs some changes with logging the team data. The format is fine, but it needs to add to the data already in S3 (if the file exists)
sebtheo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few nits
TotalDwarf03
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Works as expected 👍
|
@mwirikia there were still comments in the previous review that haven't been resolved yet |
* Update to remove nan rows in the dataset * Add functionality to get team history from the Github API * add documentation of the team historic metrics * add support for query params - since * update docs
What type of PR is this? (check all applicable)
What
Functionality to get teams history saved as json.
{ "team" : team_name, "data" : list of daily Copilot usage metrics }Testing
Have any new tests been added as part of this issue? If not, try to explain why test coverage is not needed here.
Please write a brief description of why test coverage is not necessary here.
Documentation
Has any new documentation been written as part of this issue? We should try to keep documentation up to date
as new code is added, rather than leaving it for the future.
Please write a brief description of why documentation is not necessary here.
Related issues
Provide links to any related issues.
How to review
Describe the steps required to test the changes.