@Bauer - that was another one where it was multiple PR's with with multiple commits on the same file in the same PR. When I start looking at those, I just move on to something else. For future reference, the way to do it is:
When you start work on a new feature, on your fork, create a new branch. Edit your files, and test. Don't commit anything until you are sure everything is working. Even when you are sure, test for a few more days. THEN hit commit, push and create the PR. I'm not sure how you work, whether you have an IDE locally, and set up and 'upstream' remote pointing at the Fabrik repo, or whether you manually do the PR's from the github web UI. So exactly how you submit the PR depends on that.
This way, there's only one commit on each file (not a series of commits that change the same lines of code multiple times), and they are all collected in one PR, and with one click I can merge it into a "feature branch" on my end, and see all the changes. With multiple PR's, it makes it really hard for me to create a feature branch where I can test your changes, before actually merging them into the live code. And because I'm a) lazy and b) very busy, if something is Really Hard, I tend to procrastinate.
I'm more than happy to help tutor you on github usage - I've offered before.
BTW - he seems to be talking about the "Copy" button on the form, not a list a copy.
-- hugh