Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/publish.yml
Original file line number Diff line number Diff line change
Expand Up @@ -25,8 +25,8 @@ jobs:

- name: Setup git user
run: |
git config user.name "Abhay V Ashokan"
git config user.email "abhay.ashokan@bigbinary.com"
git config user.name "Yedhin Kizhakkethara"
git config user.email "yedhin@bigbinary.com"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hardcoding a specific individual's name and email associates all automated workflow commits with their personal account. It is generally recommended to use the standard GitHub Actions bot account to clearly distinguish automated actions from human commits and to avoid issues if the individual changes roles or leaves.

Click to see review metadata
{
  "confidence": 0.9,
  "severity": "trivial",
  "suggested_fix": "Consider using the standard GitHub Actions bot credentials, such as setting the name to 'github-actions[bot]' and the email to '41898282+github-actions[bot]@users.noreply.github.com'.",
  "verification_questions": [
    "Is there a strict organizational requirement for these automated commits to be attributed to a specific individual rather than a generic bot?"
  ]
}


- name: Setup NodeJS LTS version
uses: actions/setup-node@8c91899e586c5b171469028077307d293428b516
Expand Down