Hi Ed,
First, again, my apologies for the issue spam. While I was working on my own fork (now ~80 commits ahead, I'd love to chat about what may be more generalisable back to your setup) I was causing it to generate issues. While working in my main project, that was just fine. It turns out that here, gh sends issues upstream when it detects its on a forked repo.
Would you like me to contribute a PR for getting-started or the skill that creates local setup files to check if the plugin is a fork or not? I feel deeply ashamed of the AI spam that I caused and am fully at fault for. I have now confirmed that on both my computers running my fork, the upstream repo for gh is set to my own repo rather than yours.
Sorry again,
-Brian
Hi Ed,
First, again, my apologies for the issue spam. While I was working on my own fork (now ~80 commits ahead, I'd love to chat about what may be more generalisable back to your setup) I was causing it to generate issues. While working in my main project, that was just fine. It turns out that here, gh sends issues upstream when it detects its on a forked repo.
Would you like me to contribute a PR for getting-started or the skill that creates local setup files to check if the plugin is a fork or not? I feel deeply ashamed of the AI spam that I caused and am fully at fault for. I have now confirmed that on both my computers running my fork, the upstream repo for gh is set to my own repo rather than yours.
Sorry again,
-Brian