We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
We already have an open collective account, apparently GitHub gives us a way to display it. We need to have vegastrike apply to GitHub though.
vegastrike
More details: https://help.github.com/en/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors https://help.github.com/en/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/ https://help.github.com/en/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository
The text was updated successfully, but these errors were encountered:
We'd need to add the FUNDING.yml to each repository - namemly the engine and perhaps UtCS assets.
Sorry, something went wrong.
Will approve when we have things up to dare
I have added the file and button to the two Assets repos and to the website repo. To the engine repo I have opened a PR
BenjamenMeyer
Loki1950
nabaco
No branches or pull requests
We already have an open collective account, apparently GitHub gives us a way to display it. We need to have
vegastrike
apply to GitHub though.More details:
https://help.github.com/en/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors
https://help.github.com/en/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors
https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/
https://help.github.com/en/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository
The text was updated successfully, but these errors were encountered: