Thank you tom for the info and thank you for moving the topic to the subcategory.
I actually didn’t find that when creating but will take a more closer look the next time.
Is there anything I can do to put a github token into travis (never used it in any way) or can you provide it?
I’m not sure whether or not this is anything I can do or not. I’m glad if I can help and understand the processes a bit better.
Regarding the order of updates to code and guides, that is on me I suppose. I had little insight on the processes. I’ll put it on the .NET SDK project board to check the guide for changes required based on the last PR by alex.
As alex and me discussed on the repo itself, we consider the current state of the master branch a pre-release and have marked it as such on the releases section and on nuget.
Is there a way to provide guide and api references for both (in case of API it doesn’t look to me though when it should do it automated) the last version 1.7.0 and the new 2.0.0 or will we need to prepare the changes and decide to switch from the one to the other?
Or should changes for a newer version be included in the old guide and marked as related to the new version in some way? (perhaps I’m overcomplicating it ^^)