-
-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: outputs the error messages #194
Merged
Merged
Changes from 1 commit
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
958060d
feat: outputs the error messages
juninholiveira 4f18557
style: run eslint src --fix
juninholiveira a0adbcd
fix: setOutput never getting called
juninholiveira 278a1ec
refactor: remove unused variable
juninholiveira 7c2e077
refactor: remove unused call
juninholiveira 8f50de9
refactor: change output name to official docs style
juninholiveira 1800f47
feat: create new workflow to test output messages
juninholiveira eae7697
docs: add information about outputs on readme.md
juninholiveira 44f0be2
Lowercase error_message
amannn cb5e1ae
Shorten docs
amannn 70b5725
Improved example
amannn File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
fix: setOutput never getting called
- Loading branch information
commit a0adbcd590aebb2315cb08c0f654cefc35a1a975
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have some reasoning on why you picked
error_message
? Generally we use camelCase, so in doubt I'd go for that here too. It would also be good to do some research if there is some existing convention from other actions that we could align ourselves to.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, I only based my choice on the Conventional Changelog Action, which uses snake_case for the outputs.
https://github.com/TriPSs/conventional-changelog-action
I can look into some more famous examples, but the final decision is yours xD what do you prefer? camelCase?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I recommend using as it is in docs, upper case and underscore
https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea, base it on docs seems like the best option imo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the suggestion @derberg!
I just checked the docs and it seems like they're a bit inconsistent with the casing:
It seems like there's unfortunately not really a standard here. However lower case snake case seems to be the most popular one and also what convitional-changelog-action is using, so I'd vote to go for that.