Add react-native-permission-gate

[cengizemre]

Adds react-native-permission-gate headless permission-flow orchestration for React Native: a state-machine hook (usePermission / usePermissions), rationale gating, blocked → Settings routing, focus re-validation, and app-wide native-prompt serialization. Built on top of react-native-permissions, fully typed, adapter-agnostic core with unit tests. Published on npm as react-native-permission-gate (MIT).

[Simek]

Hey @cengizemre, thanks for adding a new entry to the directory! 👍

Unfortunately it looks like your repository/account setting prevents project data access via GitHub GraphQL API. We recently have the similar issue in #2664, but it got resolved by the author.

[cengizemre]

Hey @Simek,

Thanks for taking a look I appricate, and for the pointer to #2664.

I looked into this. I ran your GitHubRepositoryQuery against my repo with a token and it returns full data with no errors: the repository resolves, isPrivate is false, the package.json blob reads correctly with the name react-native-permission-gate, license is MIT, and the file tree loads. The npm downloads endpoint returns data too (api.npmjs.org/downloads/point/last-month/react-native-permission-gate). The repository is public and I couldn't find any setting on my end that restricts API access.

So from my side the data looks fully fetchable, which makes me think this was a transient GraphQL fetch on the CI run rather than a setting on my account, similar to how #2664 resolved on a fresh run. I already closed and reopened the PR once, but that retry landed on the same result. Could you re-run the check when you have a moment? Happy to help with anything else. 🙏🏻

[Simek]

Thanks for checking @cengizemre!

This issue become a thing in recent days, and it only happen on certain PR, not sure why to be honest (maybe GH runner receives lower permissions token when triggered from external branches?). Will need to check if anything changed on the GH side.

The weird part is that is inconsistent, it works fine in other contributions like #2673 or #2674. Can you try closing and creating new PR?

[Simek]

Hey @cengizemre, can you try rebasing the PR against the current main?

I just shipped a workaround which hopefully should help in #2680.