-
Notifications
You must be signed in to change notification settings - Fork 11
Open
Description
I set up a simple issue and tagged it, but it appears Aider does "one shot" and returns without editing files.
Scanning repo: 100%|██████████| 569/569 [00:03<00:00, 151.62it/s]
To implement this feature, we'll likely need to modify files related to
challenge/course perks display and access control. Based on the file summaries
provided, I don't see the specific files that would handle challenge perks
visibility.
I would need to see and potentially modify files like:
1 The component that displays challenge perks
2 Any authorization rules related to challenge access
3 The API route that serves challenge perk data
Could you please add the following files to the chat (if they exist):
1 Any files in app/(modules)/learn/components/ that handle displaying challenge
perks
2 The relevant API router file in server/api/routers/ that handles
challenge/course data
3 Any authorization rules in utils/access/ specific to challenges
Once you share these files, I can propose the specific changes needed to
restrict perk visibility to enrolled builders and challenge owners.
Tokens: 4.3k sent, 179 received. Cost: $0.02 message, $0.02 session.
Everything up-to-date
And on PR creation:
RequestError [HttpError]: Validation Failed: {"resource":"PullRequest","code":"custom","message":"No commits between main and feature/aider-challenge-perks-restrict"}
Error: Unhandled error: HttpError: Validation Failed: {"resource":"PullRequest","code":"custom","message":"No commits between main and feature/aider-challenge-perks-restrict"}
Is there a way to enable multi-turn until resolution in Aider in this action?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels