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

LIcence is always valid #136

Closed
wants to merge 1 commit into from
Closed

Conversation

PallHaraldsson
Copy link

Not "until" something:

9694ba9

@PallHaraldsson
Copy link
Author

I'm not sure this is the best text, it needs not refer to the year at all?

@irgolic
Copy link
Owner

irgolic commented Nov 21, 2023

Hey, sorry for the late response. To be crystal clear, the license is always valid. What you're reading is GPT's interpretation of the MIT license. The part you're editing is autogenerated, and the change would be reverted in its next run.

Thanks for pointing it out, interesting to see gpt-3.5-turbo get something like this wrong!

@irgolic irgolic closed this Nov 21, 2023
@PallHaraldsson
Copy link
Author

Interesting, what is the prompt? I assume the LICENSE.md file, in full, not just "MIT license" but but something more, prefix "explain the following file" that you do for any file?

@PallHaraldsson PallHaraldsson deleted the patch-1 branch November 21, 2023 22:39
@irgolic
Copy link
Owner

irgolic commented Nov 24, 2023

If you'd like to see the exact prompts, try running it with verbose: true. It'll then show you all the steps of the process in the PR.

So your trigger file should look something like this:

triggers:
  - label_substring: summarize
    on_issue: false
    on_pull_request: true
    run: summarize_pr
    verbose: true

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants