ci: pf-4128 contribution policy workflow#194
Conversation
56a7eb6 to
8674b84
Compare
8674b84 to
27b74a2
Compare
nicolethoen
left a comment
There was a problem hiding this comment.
Took a look primarily at the copy
| if (codeSignature.hasTell) { | ||
| const botComment = `### 🤖 PR Quality Guidance\n` + | ||
| `I've moved this to **Draft** due to the scope of changes, and to avoid confusion.\n` + | ||
| `Once you've focused your changes I'll take another look.\n\n` + |
There was a problem hiding this comment.
Once you've addressed these items, I'll re-check your changes. Thank you for your contribution!
| } else { | ||
| // Or confirm the work has passed pre-check | ||
| const successComment = `### 🤖 PR Quality Guidance\n` + | ||
| `I finished my scan and all pre-checks pass!\n\n` + |
There was a problem hiding this comment.
All pre-checks pass! Your contribution is queued for review. Thank you for following our guidelines!
* build, workflow package audit, policy PR gatekeeper, commits, integration * testing, scripts testing for workflows
|
So we ended up refactoring the messages again @nicolethoen ... it may alter your comments
|
27b74a2 to
b60aa20
Compare
nicolethoen
left a comment
There was a problem hiding this comment.
I added suggestions back with suggestions for the messages.
I tried removing 'you' and 'i' statements to make it sound more direct/actionable and a bit less first person.
| const errors = []; | ||
|
|
||
| if (isMaxFilesUpdated === true) { | ||
| errors.push(`⚠️ You've updated a lot of files (${fileCount}/${fileChangeLimit}). **Resolution:** To ensure a smooth review, please consider reducing the scope of these changes by splitting them into smaller, more focused PR contributions.`); |
There was a problem hiding this comment.
| } | ||
|
|
||
| if (isCoreModified) { | ||
| errors.push(`⚠️ I detected core file modifications. To help us track and plan your work, please ensure these updates are associated with a GitHub issue (${coreModified.join(', ')}). **Resolution:** Link a GitHub issue in your PR description. Starting with an issue ensures your work is recognized and aligned with the roadmap.`); |
There was a problem hiding this comment.
| } | ||
|
|
||
| if (isSecModified) { | ||
| errors.push(`⚠️ I've found updates to security-sensitive files (${secModified.join(', ')}). **Resolution:** These changes require a core contributor's review. You can remove these changes or provide a clear explanation for these updates in your PR description.`); |
There was a problem hiding this comment.
| } | ||
|
|
||
| if (isAgentModified) { | ||
| errors.push(`⚠️ I found modifications to agent guidelines (${agentModified.join(', ')}). **Resolution:** Changes to shared guidelines require architectural alignment. Please coordinate these updates through a GitHub issue first.`); |
There was a problem hiding this comment.
| errors.push(`⚠️ I detected core file modifications. To help us track and plan your work, please ensure these updates are associated with a GitHub issue (${coreModified.join(', ')}). **Resolution:** Link a GitHub issue in your PR description. Starting with an issue ensures your work is recognized and aligned with the roadmap.`); | ||
| } | ||
|
|
||
| if (isExtraModified) { |
There was a problem hiding this comment.
There was a problem hiding this comment.
This one we're going to have to tweak more... these lists we're leveraging can include both "test" and "code".
Inviting discussion on aligning to an established pattern vs creating an entirely new one based on an internal preference feels like an unresolvable thing (def way more talking than we want). I'll tweak it to remove the "I" for sure, but I'll fiddle with it
What is it?
Notes
Updates issue/story
related #193
updates #190
pf-4128