Peter - I meant it as a figurative example - on a master branch you can tag whenever you want right? And so you can point users to a specific tag on master so they have a stable point to load from (possibly while you merge a branch back to master and then update any documentation or config before retagging and updating a BaselineOf?
This looks like what the AWS Smalltalk git repo has used as an example. Tim (Ps Apologies for the "rage" iOS autocorrect - apparently that's what Apple thinks tags is corrected to ;) Sent from my iPhone Sent from my iPhone On 30 Jul 2017, at 16:35, Peter Uhnak <i.uh...@gmail.com> wrote: >> >> If I've understood correctly, this means you can rage master with a version >> number like v1.1 and then put that in the URL >> >>> https://github.com/peteruhnak/IconFactory/tree/master:v1.1/ > > I am not sure where you got this url from, but combining branch and tag name > makes nor sense... that's like you wanted a version 1.1 AND 2.3 (or whatever > would be the latest in master). > > (as mentioned in the syntax: branch name OR commit id OR tag id) > > Peter >
