👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

Hey @jsoref Apologies for the delay on getting back to you on this. Unfortunately this one got lost in the shuffle.

Looking at this now, it's clear that you are wanting to release from a fork but I was wondering what use case this was fulfilling from a community standpoint. We release this using the semantic release package which assumes a few things - just trying to get an idea of what were you looking to do with releasing from a fork outside of the scope of a normal release.

Let us know if you get a chance. Thanks!

@nickfloyd:
I'm not trying to release, i'm trying not to get an ❌ when I sync my fork.

I'd be perfectly happy with adding a constraint of if: github.owner == 'octokit' if you'd prefer.

@nickfloyd: I'm not trying to release, i'm trying not to get an ❌ when I sync my fork.

Thank you for the clarity! That completely makes sense.

I'd be perfectly happy with adding a constraint of if: github.owner == 'octokit' if you'd prefer.

We'd definitely prefer that approach if you have time to make the change.

🎉 This PR is included in version 13.6.3 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀