clear-pr-merge-commit-message - Limit to squash merges#9398
Conversation
Agent-Logs-Url: https://github.com/refined-github/refined-github/sessions/9fc6716f-e190-491e-acc8-6b4c5aba3364 Co-authored-by: fregante <[email protected]>
Agent-Logs-Url: https://github.com/refined-github/refined-github/sessions/9fc6716f-e190-491e-acc8-6b4c5aba3364 Co-authored-by: fregante <[email protected]>
Agent-Logs-Url: https://github.com/refined-github/refined-github/sessions/9fc6716f-e190-491e-acc8-6b4c5aba3364 Co-authored-by: fregante <[email protected]>
clear-pr-merge-commit-message - Only clear squash merge commit messages
Agent-Logs-Url: https://github.com/refined-github/refined-github/sessions/a8054dba-3b73-4592-9c0a-812da1cad5a6 Co-authored-by: fregante <[email protected]>
|
refined-github/source/features/sync-pr-commit-title.tsx Lines 42 to 52 in b323b3d |
clear-pr-merge-commit-message - Only clear squash merge commit messagesclear-pr-merge-commit-message - Limit to squash merges
|
@SunsetTechuila looks like it can be simplified in that feature since And actually, I'll open a followup PR because it looks like most optional usage there is wrong |
Wrong. |
So you're saying that code was not self-evident and a contributor didn't know when it could be optional, leading to a bad refactor? Sounds like what I said when introducing mandatory "when" comments :) |
It is if you read it carefully and know how the UI behaves 🤷♂️. But I'm not against adding a comment in this case |
Test URLs
Screenshot