-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Flag new/updated Sandcastle examples #6384
Comments
For automation, this should be easy by having |
This is a great idea. Probably shouldn't use file timestamps for this though. Git log can identify what's changed lately in a particular branch, or we could manually flag some each release. |
For example, if a developer has been working on a branch that has changed demos, and then swaps back to master to build a release, the datestamps on those files will get touched to "now" as the demos are reset back to their old master state. They would be incorrectly flagged as new. Likewise, on a fresh clone, everything is new. |
Just do: |
@mramato That's perfect. |
PR incoming. |
Right now, users have to look at CHANGES.md or I guess the file timestamps to see what new examples are in a release.
It would be cool if there was a Sandcastle tab (or other type of sorting / highlighting) where it is easy to discover the new / significantly updated examples.
Could maybe even automate it as part of the build.
Folks were asking for the same thing for three.js at GTC
The text was updated successfully, but these errors were encountered: