Closed haritha-mohan closed 1 week ago
What a fail of a PR
bro your code sucks
bro your code sucks
bro your code sucks
yo this pr sucks
bro your code sucks
bro your code sucks
bro your code sucks
bro your code sucks
bro your code sucks
more recent. bro your code sucks
bro your code sucks
bro your code sucks
bro your code sucks
bro your code sucks
this is a great pr!
this sucks
yo we back, this sucks
your code sucks
your code sucks
your code sucks
your code sucks
your code sucks
@jonathanpeppers
the feature works now! made the feature opt in, similar to how we handle commentToPost/labelToAdd parameters.
Can share a link to a place you tried it?
tested it using a sample repo: https://github.com/haritha-mohan/heat-sensor-tester/pull/1
the reason why it just shows "minimized" as opposed to "marked as abuse" is due to how GraphQL processes the action internally: see ref https://github.com/orgs/community/discussions/19865
also in case anyone uses the REST API/graph QL in the future, there is a distinction between the id vs node id🙃: https://docs.github.com/en/graphql/guides/using-global-node-ids
leveraging the existing REST call, we can get the specific comment id of interest from comment object in the payload.
then, via the GraphQL API, we can minimize the comment and mark it as abuse. don't think the client mutation id is necessary for this call..
fixes https://github.com/jonathanpeppers/inclusive-heat-sensor/issues/11