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.

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

feat: Bring Elixir library in-house #10635

Merged
merged 2 commits into from
Feb 11, 2025

Conversation

rafaeelaudibert
Copy link
Member

Changes

We've talked to @nkezhaya and he's agreed to transfer ownership of the library! It's now hosted in posthog/posthog-elixir

Copy link

vercel bot commented Feb 11, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
posthog ✅ Ready (Inspect) Visit Preview Feb 11, 2025 6:48pm

@rafaeelaudibert rafaeelaudibert enabled auto-merge (squash) February 11, 2025 17:47
We've talked to @nkezhaya and he's agreed to transfer ownership of the library! It's now hosted in posthog/posthog-elixir
Copy link
Contributor

@ivanagas ivanagas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🥳

Properly note beta/3rd party where appropriate
@rafaeelaudibert rafaeelaudibert merged commit 634f1b3 into master Feb 11, 2025
3 checks passed
@rafaeelaudibert rafaeelaudibert deleted the bring-elixir-library-in-house branch February 11, 2025 18:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants