-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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(templates/deno): deploying to Deno Deploy #2824
Merged
Merged
Conversation
This file contains 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
pcattori
force-pushed
the
pedro/deno-deploy
branch
3 times, most recently
from
April 15, 2022 22:45
7da0791
to
43be45f
Compare
pcattori
force-pushed
the
pedro/deno-deploy
branch
from
April 15, 2022 22:52
43be45f
to
d33cd7a
Compare
pcattori
force-pushed
the
pedro/deno-deploy
branch
2 times, most recently
from
May 19, 2022 18:28
343cc17
to
f64386d
Compare
MichaelDeBoey
requested changes
May 19, 2022
MichaelDeBoey
changed the title
feat(templates/deno-deploy): add new deno deploy template
feat(templates/deno): add Deno Deploy instructions
May 19, 2022
pcattori
changed the title
feat(templates/deno): add Deno Deploy instructions
feat(templates/deno): instructions for deploying to Deno Deploy
May 19, 2022
pcattori
force-pushed
the
pedro/deno-deploy
branch
from
May 19, 2022 18:34
7f76c22
to
335d7bd
Compare
MichaelDeBoey
approved these changes
May 19, 2022
pcattori
force-pushed
the
pedro/deno-deploy
branch
from
May 19, 2022 20:52
335d7bd
to
84f08a8
Compare
pcattori
changed the title
feat(templates/deno): instructions for deploying to Deno Deploy
feat(templates/deno): deploying to Deno Deploy
May 20, 2022
MichaelDeBoey
approved these changes
May 20, 2022
pcattori
force-pushed
the
pedro/deno-deploy
branch
from
May 21, 2022 14:09
e13fcc9
to
84def56
Compare
pcattori
force-pushed
the
pedro/deno-deploy
branch
from
May 21, 2022 19:19
84def56
to
9975428
Compare
mcansh
approved these changes
May 21, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🦕☄️
eastlondoner
pushed a commit
to eastlondoner/remix
that referenced
this pull request
Jun 8, 2022
* feat(templates/deno): deploy to deno deploy * feat(templates/deno): recommend the deno extension for vscode * docs(templates/deno): explain how to setup type hints within editor * ci(deno-deploy): add deploy test for deno deploy
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.
Testing Strategy
Deployment test for Deno Deploy.
Tried the test locally by using my own Deno Deploy project name, and that deployed successfully. (https://salty-bee-35.deno.dev/)