Merge FlyCode Config PR
After you finished the configuration form from the previous step, you should've been redirected to this final page in our onboarding process:
Merge FlyCode's config PR
Now, all that's left to do is to merge the FlyCode config PR and you're done!
What does this PR contain? Well, I'm glad you asked. This PR contains just 1 file -
.flycode.yaml, an an auto-generated file which configures how FlyCode works with your project and where it looks for text resources. It was auto-generated based on the form you filled in the last step, so it's tailored just for you!To merge the PR with maximum convenience, we've place a
Go to GitHub button (as seen in the image above) that'll take you to your repository's Pull Requests tab, where you'll find a new open PR with the title Add FlyCode Configuration. Now all that's left to do is merge it, then head back to FlyCode to finish the process.
This is how it should look like when the PR was successfully merged:
FlyCode's config PR merged successfully
Now, all that's left to do is click on the
Take me to my App button! 🎉
In the event that the FlyCode configuration PR ran into an error while merging, or an error has occurred after the merge, this will be shown instead of the success message:
Setup failed
In this case, there are 2 things you can do:
- Review the docs, specifically the
.flycode.yamlconfiguration section. Maybe the parameters provided in the.flycode.yamldidn't correspond to the text resources in your project. Try checking that the base directory, text resource path and text format are correct. - Book a session with us, and we'll solve this issue together.
Last modified 2mo ago