Description
When using the recent-activity action, PushEvent entries show "undefined commit(s)" instead of the actual number of commits in the push.
Expected Behavior
Should display something like:
?? Pushed 3 commit(s) to [username/repo](url)
Actual Behavior
Displays:
?? Pushed undefined commit(s) to [username/repo](url)
Workflow Configuration
- name: Generate github activity
uses: Readme-Workflows/recent-activity@main
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}With config file:
user: username
maxLines: 10
Debug Logs
☴ debug Getting activity for username
☴ debug 63 events found for username.
[
"⬆️ Pushed undefined commit(s) to [username/repo](https://github.com/username/repo)",
"⬆️ Pushed undefined commit(s) to [username/repo2](https://github.com/username/repo2)",
...
]
The serializers show PushEvent is correctly recognized, but the commit count is not being extracted properly from the GitHub API payload.
Environment
- Action version:
@main (also tested with @v2.4.1)
- Runner:
ubuntu-latest
Additional Context
The action successfully finds and processes PushEvent (as shown in debug logs), but the commit count variable is undefined. This suggests the property name or structure in the GitHub Events API payload may have changed, or there's an issue with how the commit count is being extracted.
Description
When using the
recent-activityaction, PushEvent entries show "undefined commit(s)" instead of the actual number of commits in the push.Expected Behavior
Should display something like:
?? Pushed 3 commit(s) to [username/repo](url)Actual Behavior
Displays:
?? Pushed undefined commit(s) to [username/repo](url)Workflow Configuration
With config file:
Debug Logs
The serializers show PushEvent is correctly recognized, but the commit count is not being extracted properly from the GitHub API payload.
Environment
@main(also tested with@v2.4.1)ubuntu-latestAdditional Context
The action successfully finds and processes PushEvent (as shown in debug logs), but the commit count variable is undefined. This suggests the property name or structure in the GitHub Events API payload may have changed, or there's an issue with how the commit count is being extracted.