fix: rename flatpak files from DevPod/loft to Devsy#9
Conversation
The workflows reference sh.devsy.devsy.yml, Devsy.desktop, and devsy-wrapper but the files were still using old names. This caused the flatpak build job to fail with "No such file or directory".
✅ Deploy Preview for devsydev canceled.
|
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 41 minutes and 14 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ 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 |
) (#94) When the default value in ${localEnv:VAR:default} contains colons (e.g., http://proxy:8080), only the first segment was returned because args[1] discards everything after the first colon. Use strings.Join(args[1:], ":") to rejoin the full default value.
1 participant
Summary
desktop/flatpak/sh.loft.devpod.yml→sh.devsy.devsy.ymldesktop/flatpak/DevPod.desktop→Devsy.desktopdesktop/flatpak/devpod-wrapper→devsy-wrapperThe workflows already reference the new names but the files were never renamed, causing the flatpak build to fail with
sed: can't read .../sh.devsy.devsy.yml: No such file or directory.