feat: add commit-author for customization

[srivatsan0611]

Summary

This PR adds a new optional input to enhance commit customization:

• commit-author: Allows specifying a custom commit author in format "Name "

Changes

• Add commit-author input to action.yml
• Implement input parsing with validation (warns on invalid author format)
• Add comprehensive test coverage for the feature
• Update documentation with examples

Test Plan

• All existing tests pass (33/33)
• New tests cover:
  • Valid author format parsing
  • Invalid author format handling with warning
  • Valid multi line message handling as an additional check

[dsanders11]

Hi @srivatsan0611, thanks for the PR! I'll take a deeper look at this when I get some time.

Quick question - does commit-body need to be a separate input, or could you simply use a multi-line message input and have it work as expected?

E.g.

message: |
  This will be the the one-line title
  
  Another line
  
  Closes #0000

[srivatsan0611]

Hi @srivatsan0611, thanks for the PR! I'll take a deeper look at this when I get some time.

Quick question - does commit-body need to be a separate input, or could you simply use a multi-line message input and have it work as expected?

E.g.

message: |
  This will be the the one-line title
  
  Another line
  
  Closes #0000

Hi @dsanders11, Thanks for taking a look!

Great question about commit-body vs multi-line message. You're absolutely right that multi-line message could work:

message: |
feat: add new feature

This is the body
Closes #123

My reasoning for the separate input was:

1. Explicitly separates title from body (mirrors git's concept of subject vs body)
2. Automatically adds the blank line separator, so users don't forget
3. Some Actions use separate inputs (e.g., pull_request_title + pull_request_body)

But honestly, your approach is simpler and more flexible. Users already know multi-line YAML syntax, and it reduces the API surface, if you prefer that approach. Let me know what you think!

[dsanders11]

But honestly, your approach is simpler and more flexible. Users already know multi-line YAML syntax, and it reduces the API surface, if you prefer that approach. Let me know what you think!

Yea, I'd prefer to have just one message input and remove the commit-body input from this PR.

[srivatsan0611]

Yea, I'd prefer to have just one message input and remove the commit-body input from this PR.

Thanks for the feedback @dsanders11 . I have now:

• Removed commit-body input from action.yml
• Removed message concatenation logic in main.
• Updated tests and docs to use multi-line message directly

I've still kept a "multi line" test cuz I thought that maybe test ensures that messages containing newlines (like the example above) are correctly passed through to the GitHub API.
It validates that the action doesn't mangle with multi-line messages which I felt was important since that's the intended way to create commits with bodies.
Please do go through it again, thanks a ton for your time!

[srivatsan0611]

hi @dsanders11 just a quick follow up. were you able to go through the PR, would you like me to do something else?