Skip to content

feat(doc-style): reporter is defined based on the event#1158

Open
vgelbgras wants to merge 2 commits intomainfrom
feat/doc-style/reporter
Open

feat(doc-style): reporter is defined based on the event#1158
vgelbgras wants to merge 2 commits intomainfrom
feat/doc-style/reporter

Conversation

@vgelbgras
Copy link
Contributor

This pull request makes a small change to the doc-style/action.yml file, updating the logic for the reporter parameter to dynamically select the reporter type based on the event name. This improves compatibility with both pull request and push events.

@vgelbgras vgelbgras requested a review from a team as a code owner February 16, 2026 15:04
@github-actions github-actions bot added the enhancement General improvements to existing features label Feb 16, 2026
@vgelbgras vgelbgras self-assigned this Feb 16, 2026
Copy link
Contributor

@SMoraisAnsys SMoraisAnsys left a comment

Choose a reason for hiding this comment

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

Thanks for the contribution @vgelbgras
I think our main use case for this action was for PR events but it's fine to extend it for push events. Could you investigate the direct use of 'github-check' as a default value (no conditional) ?

with:
files: ${{ inputs.files }}
reporter: github-pr-check
reporter: ${{ github.event_name == 'pull_request' && 'github-pr-check' || 'github-check' }}
Copy link
Contributor

Choose a reason for hiding this comment

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

From the description here I would even consider changing to 'github-check' directly.
Could you give it a try and see how it works on your side ?

Copy link
Member

Choose a reason for hiding this comment

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

Yeah agreed - seems like github-check would work in all scenarios, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Could we have it as input with a default value (github-check) so it is more flexible?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement General improvements to existing features

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants