Conversation
✅ Deploy Preview for agentscan ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThis pull request fixes two typos in test suite descriptions: "idendity-replicant" → "identity-replicant" in Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@jsoref Since I've just pushed a new GitHub action, would you mind updating the branch? I want to see if it works. It probably won't because the PR is already opened. |
|
PS: Thanks for fixing the typo! 🙏 |
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
|
It won't. You're using |
|
Yeah, that won't work. You're using You'd want to use a Keep in mind that any time a PR from a fork talks to your CI w/ write permissions, you're asking to be attacked. |
|
It was working from a PR in this repo (#20), but I didn't account for the permissions differences in a fork. 🤔 |
|
If you are up for some action, you can do the same trick of ope/close; otherwise, I'll just approve this one and call it a day 🤣 |
|
Instead of (only) trying to post a comment, you should output a |
|
I think I'll need more practice with this one. Since you seem to be familiar with actions, and this is literally my first attempt, you're more than welcome to contribute to that. I will probably move it to its own repo, but I just wanted to try it "locally" first. |
|
This is probably good enough to get you going: https://devopsjournal.io/blog/2023/06/08/GITHUB_STEP_SUMMARY I don't generally use octokit -- https://check-spelling.dev/ is written w/o it... anyway, best wishes. |
Hi,
No, this is not an automated PR. I have to think about things.
I actually struggled to generate this PR because initially when I was looking, all I saw was the misspellings in the
.snapfile, I was really unlucky and when I tried manually searching in vscode, I still missed the hits intest/verified-automations.test.ts.Anyway, if you're morbidly curious, you can see what I did: https://github.com/check-spelling-sandbox/agentscan/actions
Summary by CodeRabbit