Conversation
New page with information about BOSC panels for 2026
for more information, see https://pre-commit.ci
| - Contribution guidelines: balancing scale and utility of AI-assisted development with community-building | ||
| - How should an open source project assess pull requests from AI agents? | ||
| - Are zero-tolerance bans on submissions generated using AI reasonable? (e.g., https://medium.com/@livewyer/ai-disruption-to-open-source-software-oss-377f10be2d8a) | ||
| - How should an open source project assess pull requests from AI agents? |
There was a problem hiding this comment.
Looks like the edits to this file just remove spaces at the ends of a few lines - did those matter?
There was a problem hiding this comment.
It's an automatic style thing - it should/would have been caught and fixed locally before the commit was accepted (via a git pre-commit hook) if you did the edit on your local computer rather than the GitHub webeditor.
(The concept is much more powerful on code where syntax errors are much more significant motivation)
| parent: 'about' | ||
| url: 'donate' | ||
| weight: 7 | ||
| weight: 7 |
There was a problem hiding this comment.
this change also doesn't seem to do anything. i'd prefer not to have these no-op commits; they just make it slightly more difficult to figure out the actual change history of a file. can you describe how this happened? it's not a big deal; i'd just like to avoid no-op commits in the future.
There was a problem hiding this comment.
It happened earlier in f736d45 which accidentally added the unwanted trailing space.
| @@ -0,0 +1,38 @@ | |||
| --- | |||
There was a problem hiding this comment.
looks great, thanks so much for creating it! i will merge it and then we can see if anything needs to be tweaked.
3 participants
New page with information about BOSC panels for 2026