FlyCode Pull Requests

Everything about the PRs we create for you!
After you or a team member has requested changes, FlyCode automatically creates a Pull Request with those changes to the code, and plenty of useful information about the changes that were made.
Sidenote for the devs - don't worry about FlyCode spamming your PRs tab with a fresh PR for each change requested: as long as a FlyCode PR is open, all changes requested will be committed there. Only when you've closed a PR, a new one will open with the next changes.
The FlyCode PR looks like this:
FlyCode's PR
Let's see what we have here:
  • Changed Texts: here we have an interactive diff menu, with all the keys (and their locale) that were changed. In the event of a hardcoded format, the name and path of the component will display:
React hardcoded text
These keys are collapsable, and when opened they will show the text's diff (before and after the change). I took the liberty of collapsing the first text in the first image of this article. There, you can see that a text with the key src/index and locale of en-US was changed from Loading... to Loading.
  • Commit Comments: As you can see in the first image of this article, there is a comment at the bottom. Each time changes are requested, the requestor is prompted to write a descriptive message regarding the changes that are being requested. I mentioned before that as long as a FlyCode PR is open, each time changes are being requested, a new commit is pushed to the same PR with those changes. So, for each commit with new changes, there is a comment with information about the specific commit, so we know what was done, when it was done and by whom. The contents of these comments contain the message the requestor input upon requesting the changes, along with the name (or email, in some cases) of the requestor. If there isn't a message in the comment, the requestor didn't provide one - it's optional.
  • Files changed: in the Files changed tab you can see the changes FlyCode made to your code. We will never change anything that wasn't requested. Notice that the changes are also in place, which means there isn't any funky formatting happening, but rather a simple replace.
Once you're satisfied with the changes that were made in this PR, you can simply merge it. That's it! Your changes are in the code - easy as that.