You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 16, 2023. It is now read-only.
This is arguably out of scope for Mariner as described, but there is enough overlap in methodology that we should discuss adding it. If we don't add it, maybe it's a unique project by itself that uses some shared functionality.
While we interrogate the GitHub API for new issues in the repositories, we could also identify repos that have signed up for GitHub Sponsors.
If I recall correctly, the original version of Mariner did this by:
checking for the existence of a .github/funding.yml file in the repo
checking for the existence of a .github/fundint.yml file in the organization
The REST API will return a sponsorable flag for individual users, but it does not appear to return a sponsorable flag for orgs or repos.
The GraphQL API exposes a Sponsorable property that only applies to Orgs or Users. In the past I'd seen where individual projects were signed up for sponsors but the Org or User who owned them were not, but I'm not clear on the current state.
The end goal would be to ask Mariner for a separate, distinct list of "repos that could be sponsored" to provide another mechanism for supporting these projects, beyond identifying issues that match a subset of tags.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is arguably out of scope for Mariner as described, but there is enough overlap in methodology that we should discuss adding it. If we don't add it, maybe it's a unique project by itself that uses some shared functionality.
While we interrogate the GitHub API for new issues in the repositories, we could also identify repos that have signed up for GitHub Sponsors.
If I recall correctly, the original version of Mariner did this by:
The REST API will return a sponsorable flag for individual users, but it does not appear to return a sponsorable flag for orgs or repos.
The GraphQL API exposes a Sponsorable property that only applies to Orgs or Users. In the past I'd seen where individual projects were signed up for sponsors but the Org or User who owned them were not, but I'm not clear on the current state.
The end goal would be to ask Mariner for a separate, distinct list of "repos that could be sponsored" to provide another mechanism for supporting these projects, beyond identifying issues that match a subset of tags.
The text was updated successfully, but these errors were encountered: