Skip to content

Create README.md Hodges database - #836

Closed
goastpepper13-glitch wants to merge 1 commit into
gwsw:masterfrom
goastpepper13-glitch:master
Closed

goastpepper13-glitch wants to merge 1 commit into
gwsw:masterfrom
goastpepper13-glitch:master

Conversation

@goastpepper13-glitch

Copy link
Copy Markdown

Update

@goastpepper13-glitch goastpepper13-glitch left a comment

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update

@avih

avih commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

This PR doesn't create any readme file.

You need to explain in details what this is about, and why it's good to have in this repository.

All these should be with good commit title and good commit message. With details.

@gwsw

gwsw commented Oct 5, 2026

Copy link
Copy Markdown
Owner

I don't understand this PR at all. The title refers to README.md, but there is no such file, either before or after this PR is applied. It refers to something called a "Hodges database" but I have no idea what that is. The workflow runs make without running make -f Makefile.aut, so it's going to fail. It tries to run make distcheck but there is no such target in any Makefile.

Did you submit this to the wrong repository?

@avih

avih commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

Most probably someon using AI without knowing what they're doing. I suggest to close it and not waste any time on it.

@gwsw

gwsw commented Oct 5, 2026

Copy link
Copy Markdown
Owner

PR makes no sense and submitter is noncommunicative.

@gwsw gwsw closed this Oct 5, 2026
@avih

avih commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

The workflow runs make without running make -f Makefile.aut, so it's going to fail.

When suspecting that a PR is LLM nonsense, it's better to not tell them exactly what's broken, otherwise their LLM would just read your reply and address every issue you mentioned, and it would still remain nonsense, just now with more things to review.

That's why in my comment I was intentionally general. I did of course also notice quite a few of the issues you mentioned, but did not want to tell them what they need to fix, because indeed it's overall nonsense. The issue is not the bugs in the PR, it's the PR itself.

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.

3 participants