You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there an existing issue that is already proposing this?
I have searched the existing issues
Is your feature request related to a problem? Please describe it
When I execute workflows via GitHub Actions, it does not display the commit message, like it does when I execute with the direct integration. You can see both here:
Describe the solution you'd like
I'd like to see the commit message, not just the git hash to identify what code is being tested.
Ideally, users would just start to see the commit message as they do in the direct integration.
What is the motivation / use case for changing the behavior?
This will help users more quickly identify what is being tested, rather than forcing them to check their git log to see which commit SHA corresponds to which commit message.
The text was updated successfully, but these errors were encountered:
prpetten
changed the title
Request: Commit Message not displayed in CircleCI (like they did with direct GitHub integration)
Request: Commit Message not displayed in CircleCI (like they did with native GitHub integration)
Feb 6, 2024
prpetten
changed the title
Request: Commit Message not displayed in CircleCI (like they did with native GitHub integration)
Request: Commit Message not displayed in CircleCI (like they do with native GitHub integration)
Feb 6, 2024
prpetten
changed the title
Request: Commit Message not displayed in CircleCI (like they do with native GitHub integration)
Request: Commit Message not displayed in CircleCI (unlike native GitHub integration where commit messages are displayed)
Feb 6, 2024
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
When I execute workflows via GitHub Actions, it does not display the commit message, like it does when I execute with the direct integration. You can see both here:
Describe the solution you'd like
I'd like to see the commit message, not just the git hash to identify what code is being tested.
Teachability, documentation, adoption, migration strategy
Ideally, users would just start to see the commit message as they do in the direct integration.
What is the motivation / use case for changing the behavior?
This will help users more quickly identify what is being tested, rather than forcing them to check their git log to see which commit SHA corresponds to which commit message.
The text was updated successfully, but these errors were encountered: