-
Notifications
You must be signed in to change notification settings - Fork 67
Conversation
```bash | ||
# git remote set-url [remote] [url] | ||
git remote set-url origin [email protected]:owner/project.git | ||
``` |
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.
per your comment on the issue about this being "out-of-the-box" on vercel.. is this supported on vercel? only a few months ago this was commented: https://github.com/vercel/vercel/discussions/4566#discussioncomment-125253
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.
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.
Very interesting - all I know is that this project deployed to Vercel w/o issue.
Wonder if they didn't adjust the default permissions for the GH access key so that it would have access to private repos by default, can't think otherwise how it didn't fail.
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.
this is great!!! as somewhat discussed on the issue, this will help me remember to include this in any new netlify documentation for next.js :) thanks so much!!
- Put back next/image support ([#158](#158)) - Fix: strip file extension when checking if route is dynamic ([#155](#155)) - Fix: prevent copy of .public to .public ([#146](#146)) - Fix: add check if pages-manifest exists before reading ([#147](#147)) - Fix: throw error if .next/static cannot be found ([#148](#148)) - Fix: remove unnecessary * from headers rule ([#152](#152))
This draft makes small accessibility changes regarding heading hierarchical headings, and adds a foonote about private submodules.