Conversation
|
👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with |
64384d9 to
a3a1145
Compare
a3a1145 to
79637e0
Compare
79637e0 to
8f8da76
Compare
deiga
left a comment
There was a problem hiding this comment.
Half-way through, looking good so far!
8f8da76 to
d6872d3
Compare
d6872d3 to
b273abd
Compare
b273abd to
337b854
Compare
94d69ba to
86c88d6
Compare
86c88d6 to
e2e13b1
Compare
e2e13b1 to
f992480
Compare
deiga
left a comment
There was a problem hiding this comment.
There are a couple tests commented out in this PR. They seem to cover functionality which isn't covered otherwise, are those just WIP refactoring or is there some other purpose?
|
@nickfloyd @deiga I think this PR is ready to be merged. All of the tests I'm able to run locally have been run and passed. |
nickfloyd
left a comment
There was a problem hiding this comment.
Only found one super small thing! 👍
Signed-off-by: Steve Hipwell <steve.hipwell@gmail.com>
Resolves #2983
Resolves #2984
Resolves #2985
Resolves #3006
Closes #2941
Before the change?
After the change?
Pull request checklist
Does this introduce a breaking change?
Please see our docs on breaking changes to help!