Skip to content

Add Mastodon Icon #70

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.

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

Closed
wants to merge 2 commits into from
Closed

Conversation

timnolte
Copy link
Contributor

@timnolte timnolte commented Oct 20, 2018

Fixes issue #67 also to possible prepare the icon library for use by JetPack Publicize Mastodon support and potentially JetPack Sharing Mastodon support.

* Adds built Mastodon files.
* Updates existing build with support for new Mastodon icon.
@vskjefst
Copy link

Any chance of getting the merge conflicts resolved, and this PR merged to master? Would love to have the Mastodon icon in there.

@timnolte
Copy link
Contributor Author

@vskjefst I can take a look at what the merge conflict is. Seems like merging is up to repository maintainers.

@vskjefst
Copy link

vskjefst commented Jul 3, 2019

@ockham what's the chance of getting this PR merged when @timnolte has fixed the merge conflict?

@colincwilliams
Copy link

Bumping this PR given the recent meteoric rise in popularity of Mastodon. Understand if there's reasons it can't be a priority, but I figure it should be re-evaluated if it hasn't been already since things have changed.

(Yes, I want to use the icon on my site through this repo so I'm personally biased. But surely I'm not the only one. :))

jeherve added a commit that referenced this pull request Feb 1, 2023

Verified

This commit was signed with the committer’s verified signature.
jeherve Jeremy Herve
This should replace an existing PR that's currently outdated: #70.

Co-authored-by: "tim.nolte" <tim.nolte@ndigitals.com>
@jeherve jeherve mentioned this pull request Feb 1, 2023
@jeherve
Copy link
Member

jeherve commented Feb 1, 2023

@timnolte Thanks a lot for the PR! It was a bit outdated (our fault, sorry, it's taken us quite some time to get to your request!), so I ended up creating #115 to replace this PR. I'll see about getting us moving in that other PR.

@jeherve jeherve closed this in #115 Feb 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants