[GH-ISSUE #589] [Feature]: Add AI contribution policy to repo #386

Closed
opened 2026-05-06 12:28:59 +02:00 by BreizhHardware · 2 comments

Originally created by @stringlapse on GitHub (Mar 4, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/589

Originally assigned to: @maziggy on GitHub.

Problem or Use Case

It is currently unclear if AI assisted contributions are allowed.

Proposed Solution

Add AI policy to contributor guidelines. It should state if AI assisted contributions are allowed, which kinds are allowed, to what extent they are allowed, and, if allowed, how contributors should disclose their use of AI tools.

Alternatives Considered

No response

Feature Category

Other

Priority

Critical for my use case

Mockups or Examples

No response

Contribution

  • I would be willing to help implement this feature

Checklist

  • I have searched existing issues to ensure this feature hasn't already been requested
Originally created by @stringlapse on GitHub (Mar 4, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/589 Originally assigned to: @maziggy on GitHub. ### Problem or Use Case It is currently unclear if AI assisted contributions are allowed. ### Proposed Solution Add AI policy to contributor guidelines. It should state if AI assisted contributions are allowed, which kinds are allowed, to what extent they are allowed, and, if allowed, how contributors should disclose their use of AI tools. ### Alternatives Considered _No response_ ### Feature Category Other ### Priority Critical for my use case ### Mockups or Examples _No response_ ### Contribution - [x] I would be willing to help implement this feature ### Checklist - [x] I have searched existing issues to ensure this feature hasn't already been requested
BreizhHardware 2026-05-06 12:28:59 +02:00
  • closed this issue
  • added the
    wontfix
    label
Author
Owner

@maziggy commented on GitHub (Mar 6, 2026):

For me it doesn't matter. Every PR is reviewed carefully before merging. If the code is "clean" it's getting merged.

<!-- gh-comment-id:4010922492 --> @maziggy commented on GitHub (Mar 6, 2026): For me it doesn't matter. Every PR is reviewed carefully before merging. If the code is "clean" it's getting merged.
Author
Owner

@stringlapse commented on GitHub (Mar 6, 2026):

Thank you for confirming your stance. I will not be recommending Bambuddy.

<!-- gh-comment-id:4014705542 --> @stringlapse commented on GitHub (Mar 6, 2026): Thank you for confirming your stance. I will not be recommending Bambuddy.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/bambuddy#386
No description provided.