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

@remotion/lambda: Allow custom Lambda function name, but warn about the consequences #3756

Merged
merged 2 commits into from Apr 22, 2024

Conversation

JonnyBurger
Copy link
Member

No description provided.

Copy link

vercel bot commented Apr 22, 2024

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

Name Status Preview Comments Updated (UTC)
bugs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 22, 2024 0:52am
remotion ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 22, 2024 0:52am

@JonnyBurger JonnyBurger linked an issue Apr 22, 2024 that may be closed by this pull request
@JonnyBurger JonnyBurger merged commit 8455f46 into main Apr 22, 2024
13 checks passed
@JonnyBurger JonnyBurger deleted the allow-lambda-function-name branch April 22, 2024 13:01
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.

--function-name Flag Doesn't Perform as Documented
1 participant