feat: Add configurable git user inputs for commit customization #73
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR refactors the hardcoded Git user credentials to configurable inputs, allowing users to customize the git user email and name used for commits while maintaining backward compatibility.
Problem
The workflow currently hardcodes the Git user email as "[email protected]" and the user name as "cloudpossebot" in
action.yml. This prevents users from customizing the commit author information to match their organization's requirements or preferences.Solution
Added two new optional inputs to the GitHub Action:
git-user-email: Git user email for commits (default: "[email protected]")git-user-name: Git user name for commits (default: "cloudpossebot")The git configuration commands now use these input variables instead of hardcoded strings:
Usage
Default behavior (backward compatible):
Custom git user:
Changes
Backward Compatibility
Existing workflows will continue to work unchanged, as the new inputs are optional and default to the original hardcoded values. No breaking changes are introduced.
This pull request was created as a result of the following prompt from Copilot chat.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.