-
Notifications
You must be signed in to change notification settings - Fork 287
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
merge release notes #247
Comments
Hi @dherman! I'd like to tackle this bug if it's still unassigned. Would I be combining all of the content from |
@seanprashad Yes, exactly :D When you bring the cli/RELEASES.md comments into RELEASES.md, wherever they reference neon issues/PRs, you can eliminate the explicit reference to neon (e.g., "#214" can just become "#214"), and wherever they reference neon-cli issues/PRs, please make those explicitly reference the old repo (e.g., "TypeScript upgrade fixes (#62, #65)" becomes "TypeScript upgrade fixes (neon-bindings/neon-cli#62, neon-bindings/neon-cli#65)"). Also, would you mind fixing up the markdown so they render as actual links? |
Got it! I will take a look at merging the two files and fixing up the markdown to render links and get back to you if I have any questions! |
Merge stuff from cli/RELEASES.md into RELEASES.md -- since the PRs reference the
neon-cli
repo either change the links to reference that repo or link to the commits.The text was updated successfully, but these errors were encountered: