Skip to content
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

get-metadata: missing 'LGTM' in comments #166

Closed
vsemozhetbyt opened this issue Feb 7, 2018 · 8 comments
Closed

get-metadata: missing 'LGTM' in comments #166

vsemozhetbyt opened this issue Feb 7, 2018 · 8 comments
Labels
discuss pr-checker Issues related to pr checker stale

Comments

@vsemozhetbyt
Copy link
Contributor

vsemozhetbyt commented Feb 7, 2018

PR: nodejs/node#18630

Command: winpty get-metadata.cmd 18630 --check-comments

Output:

------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/18630
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
--------------------------------------------------------------------------------

Missing: nodejs/node#18630 (comment)

@priyank-p priyank-p added bug pr-checker Issues related to pr checker labels Feb 8, 2018
@priyank-p
Copy link
Contributor

@vsemozhetbyt just want to confirm did the get-metadata output had something that said maclover7 approved via LGTM in comment or something along those lines? since this is all we do currently and it's not included in generated metadata.

@vsemozhetbyt
Copy link
Contributor Author

@cPhost

Full output:
√  Done loading data for nodejs/node/pull/18630
----------------------------------- PR info ------------------------------------
Title      doc: fix link in https.md (#18630)
Author     Vse Mozhet Byt <[email protected]> (@vsemozhetbyt)
Branch     vsemozhetbyt:doc-fix-link-2018-02-07 -> nodejs:master
Labels     doc, fast-track, https, ready
Commits    1
 - doc: fix link in https.md
Committers 1
 - Vse Mozhet Byt <[email protected]>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/18630
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
--------------------------------------------------------------------------------
√  Requested Changes: 0
√  Approvals: 2, 1 from TSC (cjihrig)
i  Last Full CI on 2018-02-07T21:39:06Z: https://ci.nodejs.org/job/node-test-pull-request-lite/159/
i  This PR is being fast-tracked
‼  This PR is closed

@priyank-p
Copy link
Contributor

Ok thanks, this is a bug.

@joyeecheung
Copy link
Member

joyeecheung commented Feb 8, 2018

I think we have already discussed about this. This is by design - only comments that contain nothing but LGTM will get a warning, other types of comments don't get anything at all, because there will always be "something LGTM but I am not the expert in other things", or "I cannot give a LGTM for this" or "I would want @ someone 's LGTM for this " or other types of thing that don't make them legitimate sign-offs. In the end we will have to resort to natural language processing.

@joyeecheung joyeecheung added discuss and removed bug labels Feb 8, 2018
@joyeecheung
Copy link
Member

BTW in those cases, something like #140 would be more suitable because without NLP code, humans are better at deciding if a comment with "LGTM" is legitimate sign-off

@priyank-p
Copy link
Contributor

I think we have already discussed about this. This is by design - only comments that contain nothing but LGTM will get a warning

Oh, okay it does make sense now, so this is not a bug. I glanced at the PR again quickly to get some idea all i got was we don't include in metadata which i already knew, and something that said <name>(<username>) approved via LGTM in comment) 😅.

@github-actions
Copy link
Contributor

This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.

@github-actions github-actions bot added the stale label Aug 17, 2020
@codebytere
Copy link
Member

Gonna close this one since it's pretty old and i don't think this is something there's wide interest in doing but please reopen if that's not the case!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss pr-checker Issues related to pr checker stale
Projects
None yet
Development

No branches or pull requests

4 participants