-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add AI acknowledgement checkbox and welcome comment #2624
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
base: main
Are you sure you want to change the base?
Conversation
|
It is also possible for the bot to attribute labels to first-time contributor issues and PRs. Do we want to create a I think these changes could also be complemented by an update to the contributing docs. Not a full-page discussion, but just a note similar to the message presented in the welcome comment / check box. |
echedey-ls
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Automatic labelling for statistics I guess? The automatic message seems enough of a heads-up for me.
I don't think vibe coders are going through the contrib docs, but it doesn't make any harm to include that extra info as a stance. Maybe one day AI will 'learn' that and stop vibe coders. +1 to that proposal.
Thanks for the ideas and initiative @RDaxini
|
|
||
| If AI is used for any portion of this PR, you must vet the content | ||
| for technical accuracy and compatibility with the contributing | ||
| guidelines. No newline at end of file |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| guidelines. | |
| guidelines. | |
Missing newline at the end (consistency and Git tradition)
| issue-opened-msg: | | ||
| ### Hey @{fc-author}! :wave: | ||
|
|
||
| Thanks for opening your first issue. Welcome to the community! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really want this? IMO, it's not adding any value to the conversation. Plus, an automated thanks/welcome is less welcoming than anybody of us writing a "Confirmed. Thanks for noticing that @ ...!!" message. More natural.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really want this? IMO, it's not adding any value to the conversation. Plus, an automated thanks/welcome is less welcoming than anybody of us writing a "Confirmed. Thanks for noticing that @ ...!!" message. More natural.
I was debating that in my head and then just included it in the end, but I agree with you—a personal welcome from us would be better.
| pull_request_target: | ||
| types: opened | ||
|
|
||
| permissions: {} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not needed, probably.
| permissions: {} |
Tests addedUpdates entries indocs/sphinx/source/referencefor API changes.docs/sphinx/source/whatsnewfor all changes. Includes link to the GitHub Issue with:issue:`num`or this Pull Request with:pull:`num`. Includes contributor name and/or GitHub username (link with:ghuser:`user`).remote-data) and Milestone are assigned to the Pull Request and linked Issue.Changes:
Add checkbox to PR
Add workflow to auto-generate a comment on issues and PRs from first-time contributors
Possible:
Automatically assign a label to first-time contributor issues/PRs
Update contributing guidelines with a short note on AI