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

What's the new version of 'uses: Codium-ai/pr-agent@main' ? #1479

Closed
dep opened this issue Jan 23, 2025 · 7 comments
Closed

What's the new version of 'uses: Codium-ai/pr-agent@main' ? #1479

dep opened this issue Jan 23, 2025 · 7 comments

Comments

@dep
Copy link

dep commented Jan 23, 2025

I'm getting CI errors this morning using this in my Github Action:

uses: Codium-ai/pr-agent@main

error:

Error: Unable to resolve action. Repository not found: Codium-ai/pr-agent

What should I be using instead?

@charles-poullet-unmind
Copy link

qodo-ai/pr-agent

@dep
Copy link
Author

dep commented Jan 23, 2025

You might want to update here:

https://qodo-merge-docs.qodo.ai/installation/github/

@mrT23
Copy link
Collaborator

mrT23 commented Jan 23, 2025

We moved the organization from the old company name ('codium') to the new name ('qodo')

However, from my tests, GitHub automatically forwards the request.
Codium-ai/codium-code-examples#58
https://github.com/Codium-ai/codium-code-examples/blob/main/.github/workflows/pr-agent.yaml#L19

Image

Can you elaborate more on your scenario ?

@dep
Copy link
Author

dep commented Jan 23, 2025

Image

Switching to qodo-ai/pr-agent@main fixed it though.

@mrT23
Copy link
Collaborator

mrT23 commented Jan 23, 2025

ok, weird. at my test repo it works

Image

(but the correct thing to do anyway is to update the path)

@mrT23 mrT23 pinned this issue Jan 23, 2025
@dep
Copy link
Author

dep commented Jan 23, 2025

That's wild! Yeah was working fine yesterday but not today. Either way I'm happy to be off the deprecated path.

@dep dep closed this as completed Jan 23, 2025
@RoseSecurity
Copy link

We encountered the same error in our repo but updating the name resolved it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants