I was able to replicate the issue here as well. Here is the reason:
As some point during the execution of the code Gitora fires the following query:
in_name_tx is the name of the table the trigger is on. in_schema_cd is the owner of the table. This query returns more than one row if the table is partitioned which causes the error. I didn’t know that this query could more than one row. Apparently a table partition can have the same name as the table itself.
So as of now, Gitora doesn’t work with triggers ion partitioned tables. Unfortunately, this error will keep happening even if you remove the trigger from the Gitora repository because Gitora is trying to figure out if the trigger your are executing is an instead of trigger. And the error occurs while Gitora is trying to figure out the type if the trigger.
Gitora does this because if the trigger is an instead of trigger, Gitora will put it in version control if the view it is on is in version control. The logic here is that, it doesn’t make sense to put a view to version control without its instead of trigger. Gitora is trying to make it more convenient for the developer and tries to avoid a potential mistake he might do.
So for now, disable the Gitora triggers before you edit that trigger.