Ok, I managed to redo all of the change log so that it contains the link to the commit diff now.
@draegtun I wonder if we should now do a PR to change changes
to point to this announcement?
Ok, I managed to redo all of the change log so that it contains the link to the commit diff now.
@draegtun I wonder if we should now do a PR to change changes
to point to this announcement?
If anyone has compiled ren-c on OSX or Android, please provide a link or a HOWTO
here http://rebolchat.me/t/compiling-r3-ren-c/55
Thanks,
Added in the commit logs for red-lang.
They don't seem to have any binaries automatically generated?
Done - https://github.com/metaeducation/ren-c/pull/515
Actually we don't have a complete list
For a complete list use these links:
ChangeLog + pre-built binaries
Github commits
the api.github.com
just initially gives us the last 30 commits I think.
OK I've made a change - https://github.com/metaeducation/ren-c/pull/517
CHANGES.md is now in format prescribed by http://keepachangelog.com/en/0.3.0/
Also CHANGES shortcut will jump to version number anchor (at moment we've only "used" 2.102.0 but it's a start).
So we don't jump directly to the commit that's relevant to the build
Why not just
changes: does [
browse join-of https://github.com/metaeducation/ren-c/commit/ rebol/commit
]
It looks like red only maintains the latest binaries and the others are deleted. I need to tweak my script so that it only shows the red binary downloads for the last commit.
Fixed the red-change-log script so that it only posts the binary for the very last commit ( since it seems only the last binaries are kept ).
I think CHANGES.md should just have curated list of changes (summary). So someone can quickly see, by version, whats been added, changed or deleted. For more detailed info then they use the CHANGELOG summary provided here or go to commits directly (on Github or in Git).