-
Notifications
You must be signed in to change notification settings - Fork 61
Conversation
✅ Deploy Preview for ubiquibot-staging ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
I tried locally with __dirname and when I run |
I've just tried with the following code and the config was copied to the
Could you:
|
@Venoox please make the PR a draft if its not ready for a reivew |
Now the file gets copied over but there is another issue:
|
Yeah that definitely doesn't look like a function! Perhaps they already have an open issue on this. You might also be able to experiment with pulling out the function's contents and running them without calling the function. I'm not sure. |
Which command throws this error? This one |
Yes. It seems it's an issue with top level code. If I wrap the code in a function then the error is gone. Now there are two solutions, either we read the default config in |
I don't get any errors on Perhaps you should leave this PR in its current state and open a QA issue so that we could see how it works in your repo? |
https://github.com/Venoox/ubiquibot/actions/runs/5271555816/jobs/9532609741 As I understand this error: private.ts imports helpers.ts which executes parseYAML but parseYAML is defined later in private.ts, so it's basically a dependency cycle? |
yes, seems like that perhaps here you could refactor to:
The YAML.parse() does not return a promise so it's ok to use it at the top of the file |
Seems like the issue is solved but there is an unrelated error regarding telegram bot (https://github.com/Venoox/ubiquibot/actions/runs/5275990184/jobs/9542118341) |
It's missing here https://github.com/Venoox/ubiquibot/blob/default-config/.github/workflows/bot.yml but I think it's ok to pass it empty for QA workflow runs not related to Telegram issues |
@0xcodercrane could you review this PR again? @Venoox thank you for fixing errors |
Sure! |
In terms of code review, I had a couple of changes for @Venoox but committed what I want to the |
@Venoox could you fix typescript errors? Notice there are some changes introduced by @0xcodercrane |
@Venoox thank you @0xcodercrane pls review again |
Hey @Venoox really sorry about the delay I decided to manually try and take this over but I'm having issues resolving those merge conflicts. My progress is here: |
To wrap up the issue asap.
If you @Venoox can resolve the conflicts, we will appreciate it a lot. |
Head branch was pushed to by a user without write access
@0xcodercrane I resolved the conflicts |
Thank you. To merge the PR, I will wait for the rest 2 items. @Venoox would you re-post the QA link with the latest codebase? |
Lol @0xcodercrane I think it would have made more sense to ask @Venoox to resolve the merge conflicts as the last step. Alternatively we can pause merging into development and rush merging this in so that they don't have to keep doing more unnecessary work. But due to all the merge delays lately I'm not a fan of intentionally adding to the delays. |
Ok. we can skip the QA processing for now. but need to wait @rndquu 's input for configuration changes |
The PR looks good, no need for additional config update PRs |
Resolves #327
@rndquu I think even relative path is not gonna work because the @vercel/ncc bundler doesn't put it in the build process.