lejforchrist
lejforchrist
@sergioeliot2039 Thanks. I'll get started on this PR. Please assign this issue to me under Assignees. Thanks.
@dylburger Is this issue #4057 in the backlog? It's still open under Issues.
I ran into some issues while testing the actions. Some actions are available under the Free Plan, but the rest require a Paid Plan. Here's the response I received from...
> Hi @andrewjschuang I fixed the issue with the misspelled component key. I think I ran the linter on the wrong directory and I'm not exactly sure how to discard...
> git revert d7a84d01c57c07d2b295cf9625e2ee5db6e266b I received errors: error: commit 0717bd2123b156e8234fb2a0381a3a6565b03b4d is a merge but no -m option was given. fatal: revert failed error: commit 0717bd2123b156e8234fb2a0381a3a6565b03b4d is a merge but no...
> When I ran git rebase origin/master I received these errors: error: cannot rebase: You have unstaged changes. error: Please commit or stash them.
> ```shell > git rebase origin/master > ``` Yes, I'm in the checkpoint branch. I ran git clean -fd again and then git rebase origin/master, and I still get the...
> ```shell > git add pnpm-lock.yaml && git commit -m 'update pnpm-lock.yaml' > ``` That worked, but when I tried to push my changes with git push I received the...
> > That worked, but when I tried to push my changes with git push I received the message: To push the current branch and set the remote as upstream,...
> git push -f Done. Is someone going to QA these actions? I had issues with the Waitwhile API and had some errors that could not get more details from...