Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make the SPONSORLINK_MANIFEST envvar more of a suggestion/example #140

Closed
kzu opened this issue Feb 4, 2024 · 1 comment
Closed

Make the SPONSORLINK_MANIFEST envvar more of a suggestion/example #140

kzu opened this issue Feb 4, 2024 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@kzu
Copy link
Member

kzu commented Feb 4, 2024

Based on feedback, we should perhaps mention that the default SPONSORLINK_MANIFEST is more of a default behavior when used in conjunction with the gh-sponsors tool.
@kzu kzu added the documentation Improvements or additions to documentation label Feb 4, 2024
@kzu kzu mentioned this issue Feb 4, 2024
Closed
@kzu
Copy link
Member Author

kzu commented May 7, 2024

Moving to a file-based per-sponsorable manifest.

@kzu kzu closed this as completed May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kzu