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

The README.md file for the Personalization-Builder-io example contains and incorrect URL #391

Closed
jterribile opened this issue Sep 9, 2022 · 0 comments · Fixed by #453
Closed
Assignees
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@jterribile
Copy link

The clone and deploy section of the readme for the Personalization Builder IO example contains a URL that points to a different example.
See: https://github.com/vercel/examples/tree/main/edge-functions/personalization-builder-io#clone-and-deploy

@domeccleston domeccleston added bug Something isn't working documentation Improvements or additions to documentation labels Nov 10, 2022
@domeccleston domeccleston self-assigned this Nov 10, 2022
leerob pushed a commit that referenced this issue Nov 10, 2022
### Description

personalization-builder-io example linked to statsig example: update it
to have the correct link. Closes #391

### Demo URL

N/A: README update

### Type of Change

- [ ] New Example
- [x] Example updates (Bug fixes, new features, etc.)
- [ ] Other (changes to the codebase, but not to examples)

### New Example Checklist

- [ ] 🛫 `npm run new-example` was used to create the example
- [ ] 📚 The template wasn't used but I carefuly read the [Adding a new
example](https://github.com/vercel/examples#adding-a-new-example) steps
and implemented them in the example
- [ ] 📱 Is it responsive? Are mobile and tablets considered?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants