Add sponsor file #223
Merged
Add sponsor file #223
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JonRowe
force-pushed
the
add-sponsor-file
branch
2 times, most recently
from
04d4a69 to
eec1752
Compare
JonRowe
force-pushed
the
add-sponsor-file
branch
from
eec1752 to
cad9bf9
Compare
|
Changed to ensure all common plaintext files were found (e.g. I fixed the glob) and correctly commented in yml files. Care to re-review @pirj ? See: |
pirj
approved these changes
Dec 6, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The intent of this pr is to add the sponsor file to all our controller repos with our open collective details as well as my own sponsor account (shameless plug etc) but does so via our common files, I think this should still work with our markdown files.