To get started, only takes a few minutes: sign up and create an organization. Then, sync FlyCode with your Github Organization. Do that and you're all set to start using FlyCode! From start to finish, it should take no longer than 5-10 minutes.
Of course you can! Please refer to this section of our docs for a full walkthrough on how to do that.
No! FlyCode only changes the texts and other resources that your team has requested, while making those changes in place. Additionally, FlyCode will always generate a PR including the requested changes, which can be inspected and approved before merged into your main branch.
The team at FlyCode is always working towards integrating with new development platforms. We're rolling out invites in batches to ensure the highest quality experience for new and existing customers. You can still book a time with us and share your use case
Our platform is build off a Git-based workflow, which means any edits you make are not run-time and will still need to go through your CI/CD Pipeline. If you would like to bypass the additional testing, feel free to flag PRs from FlyCode's bot to speed up the process.
After you have installed our application, FlyCode is added as a user to your GitHub organization. When an edit is made in FlyCode, a PR is automatically created by the FlyCode bot. The PR message will contain all the details about the changes that were made, so your team can review the changes easily.
Currently our platform supports text management and editing with the following formats:
- Hardcoded - we currently supported the frameworks: React, Angular, Vue, PHP and Ruby on Rails
- Resource files - PO & JSONs are supported, as well as i18n and localized resource files.
We do support hardcoded text editing! Hardcoded support is for the following frameworks:
- Ruby on Rails
If you have a different framework you wish to connect, feel free to contact us and we'll talk about it!
If you enabled
allow access domainwhen creating your organization, additional team members will automatically join your organization if they sign up to FlyCode using an email with the same domain.
Otherwise, you can always send people an invitation from the sidebar or from the organization settings page, under the
Yes, you can! Open the organizations drop down located at the left side of the header (from any page), and click the
+ Create Newbutton.
When you install the FlyCode GitHub Application, you can choose grant FlyCode access to either all or only selected repositories in your codebase.
We know that your codebase is your prized possession, and we handle it with care!
- Each scanning process runs in isolation in its own container.
- Other than loading text resources into FlyCode, no trace is left on our servers.
- FlyCode employees don't have access to your codebase.
Quite the opposite! FlyCode enables non-technical team members deliver non technical product changes such as copy, images and icons alterations, so that developers could focus on other pressing, technical tasks. By creating a PR with changes requested by non-technical team members, FlyCode enables developers to review and approve these changes asynchronously, so to not distract them from their current tasks.
No, FlyCode changes are made in a dedicated branch with an auto-generated PR. Only after a developer (or if auto-merge is enabled in GitHub) merges the PR, the changes are applied to your main code branch - just like any other technical task.
Yes - in fact, there are 3 ways to reject (or simply not implement) certain changes.
The first way, is for the developer to close the FlyCode changes PR with the changes you want to reject. This will change the texts' statuses in FlyCode from 'change requested' back to 'draft'.
The second way is by simply not requesting certain changes: when requesting changes in FlyCode, you have the ability to select only the changes you want to implement and not all of the texts that have the 'draft' status.
The third way is reverting changes through FlyCode. Even if you've already requested a change, you can always revert it to the latest 'live' version using the revert button: