-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[Docs] Add "New Features" section to README #2089
Closed
phated opened this issue
Jan 6, 2018
· 5 comments
· May be fixed by ajesse11x/PowerShell#3, Matthelonianxl/flight-manual.atom.io#2, raindigi/cloudcannon-suite#5, cdcc1969/etherwallet#7 or baophucct/PowerShell#3
Closed
[Docs] Add "New Features" section to README #2089
phated opened this issue
Jan 6, 2018
· 5 comments
· May be fixed by ajesse11x/PowerShell#3, Matthelonianxl/flight-manual.atom.io#2, raindigi/cloudcannon-suite#5, cdcc1969/etherwallet#7 or baophucct/PowerShell#3
Labels
Milestone
Comments
@phated Do you have a rough idea of what you want to emphasize? I can write a top section for the README that includes new features, migration guide link, etc. |
I think a lot of stuff is in changelog.md barring any of the stuff we've done in the past 6-8 months |
I can |
@stevelacy If you want to do an initial outline I can do some of the fluffier stuff around it. |
phated
changed the title
Docs: Add "New Features" section to README
[Docs] Add "New Features" section to README
Oct 25, 2018
Anyone want to take a swing at this? |
phated
added a commit
that referenced
this issue
Dec 6, 2018
This was referenced May 18, 2024
This was referenced May 26, 2024
This was referenced Jun 27, 2024
This was referenced Jul 4, 2024
This was referenced Jul 12, 2024
This was referenced Jul 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think it'd be great to have a "New Features" section in the readme to help people understand all of the awesome things in gulp 4.
@stevelacy want to take a crack at this? Or anyone, really.
The text was updated successfully, but these errors were encountered: