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.

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

TypeError: (e || "").replace is not a function ... #25

Closed
felixlapalma opened this issue Apr 19, 2020 · 5 comments
Closed

TypeError: (e || "").replace is not a function ... #25

felixlapalma opened this issue Apr 19, 2020 · 5 comments
Assignees
Labels
type: bug Verified problems that need to be worked on
Projects

Comments

@felixlapalma
Copy link

Hi,

Basically I run some scripts on my repository and then add and commit files. I was using your action til this morning when it started to fail. I attached the step 7_Commit changes.txt

  • Running github actions on Ubuntu latest (add-and-commit/v4)

Thanks!

@EndBug EndBug self-assigned this Apr 19, 2020
@EndBug EndBug added the type: bug Verified problems that need to be worked on label Apr 19, 2020
@EndBug EndBug added this to To do in Main board via automation Apr 19, 2020
@EndBug EndBug moved this from To do to In progress in Main board Apr 19, 2020
EndBug added a commit that referenced this issue Apr 19, 2020
@EndBug
Copy link
Owner

EndBug commented Apr 19, 2020

Hi, thanks for opening the issue!
I think I've figured out what causes that message: it should be a problem in the error handling. With that said, it means that there has been an error in the execution of the script, so I need a little help from you for the debugging.

Please try to run the workflow using the action from the master branch ("fixed"), so that we can see what's the underlying error and see what we can do ;)
You can do that by using EndBug/add-and-commit@master in your workflow.

After you do it, please let me know how it ended

@felixlapalma
Copy link
Author

Hi! thanks for your quick response!
I tried your suggestion on branch test and the workflow went smoothly. Both runs are (slightly different conditions):

All went well! Thanks again!

@EndBug
Copy link
Owner

EndBug commented Apr 19, 2020

Happy to hear that! Even though it fixed by itself I've now published the fixes in version v4.0.2: I suggest that you now put back v4 as ref in the workflow so that you don't end up accidentally using some untested version ;)
Thanks again for the issue and good luck with your project!

@EndBug EndBug closed this as completed Apr 19, 2020
Main board automation moved this from In progress to Done Apr 19, 2020
@EndBug
Copy link
Owner

EndBug commented Jul 10, 2020

@all-contributors please add @felixlapalma for bug

@allcontributors
Copy link
Contributor

@EndBug

I've put up a pull request to add @felixlapalma! 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Verified problems that need to be worked on
Projects
No open projects
Main board
  
Done
Development

No branches or pull requests

2 participants