Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Console.log does not show up #27

Closed
robinjhector opened this issue May 15, 2020 · 2 comments
Closed

Console.log does not show up #27

robinjhector opened this issue May 15, 2020 · 2 comments

Comments

@robinjhector
Copy link

robinjhector commented May 15, 2020 •
edited
Loading

Hi!

I see that you're printing console.log('Waiting ${ms} milliseconds ...') in your action code, but I can't see it when the action runs. Is it supposed to be like this? How would one output this properly?

Thanks
@hross hross mentioned this issue Jul 17, 2020
Merged
hross added a commit that referenced this issue Jul 17, 2020
@hross
Fixes up issues with the template (#36)
16ddff4 
* #27 remove console.log
* #16 change author to empty
* #30 maintain this repo 😄 
* #8 jest update for eslint
* update dependencies
* #22 generate source maps
* #21 use prepare instead of package
* add `npm run all` to run everything
@hross
Copy link
Contributor

hross commented Jul 17, 2020

Fixed to use info/debug output and added comment on how to use it: #36

@hross hross closed this as completed Jul 17, 2020
HarikrishnanBalagopal added a commit to HarikrishnanBalagopal/publish-release that referenced this issue Dec 12, 2020
@HarikrishnanBalagopal
fix: use core.info for logging, remove unused fs import
df1c068 
See actions/javascript-action#27
Need to use https://github.com/actions/toolkit/tree/main/packages/core#logging
for logging.

Signed-off-by: Harikrishnan Balagopal <harikrishmenon@gmail.com>
Merged
HarikrishnanBalagopal added a commit to HarikrishnanBalagopal/publish-release that referenced this issue Dec 12, 2020
@HarikrishnanBalagopal
fix: use core.info for logging, remove unused fs import
fdc2694 
See actions/javascript-action#27
Need to use https://github.com/actions/toolkit/tree/main/packages/core#logging
for logging.

Signed-off-by: Harikrishnan Balagopal <harikrishmenon@gmail.com>
HarikrishnanBalagopal added a commit to HarikrishnanBalagopal/publish-release that referenced this issue Dec 12, 2020
@HarikrishnanBalagopal
fix: use core.info for logging, remove unused fs import
3d7691f 
See actions/javascript-action#27
Need to use https://github.com/actions/toolkit/tree/main/packages/core#logging
for logging.

Signed-off-by: Harikrishnan Balagopal <harikrishmenon@gmail.com>
@TomasHubelbauer
Copy link

@hross Is there any way to make it so that plain console.log calls propagate to the output of the custom Action? It isn't always preferable or possible to use @actions/core and its logging methods. I tried direct process.stdout.write too but I just can't get my script to output to the workflow that is using my custom Action.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hross @TomasHubelbauer @robinjhector