Update Go Package Index

[MatrixCrawler]

This possibly fixes #192
We need to add a v in front of the versioning tags though

[MatrixCrawler]

I updated the readme with the version note and the documentation for some missing points.
i reduced the readme file as most of the stuff is covered by the documentation and i think no one really wants to read a five page Readme ;-)
But maybe i am wrong with this.

[crablab]

I updated the readme with the version note and the documentation for some missing points.
i reduced the readme file as most of the stuff is covered by the documentation and i think no one really wants to read a five page Readme ;-)

Please could you split these changes out into a separate PR? 😅 We now have a couple of PRs with large deltas and which just keep getting longer and longer. That makes it really tricky to review as it's not clear when a PR is "done", and we're ending up in endless cycles of comments as new stuff is being added all the time :)

I think it'd help with review if we can keep them tightly scoped to a particular goal, even if that means we need to come back with more PRs in the future.

[MatrixCrawler]

I updated the readme with the version note and the documentation for some missing points.
i reduced the readme file as most of the stuff is covered by the documentation and i think no one really wants to read a five page Readme ;-)

Please could you split these changes out into a separate PR? 😅 We now have a couple of PRs with large deltas and which just keep getting longer and longer. That makes it really tricky to review as it's not clear when a PR is "done", and we're ending up in endless cycles of comments as new stuff is being added all the time :)

I think it'd help with review if we can keep them tightly scoped to a particular goal, even if that means we need to come back with more PRs in the future.

Moved the readme and documentation update to #376

[yermulnik]

That makes it really tricky to review as it's not clear when a PR is "done", and we're ending up in endless cycles of comments as new stuff is being added all the time :)

+1
force pushes also make it hard to track changes linked from the email notifications.
I'd suggest either to force-push right before the merge, or (preferably) rely upon GH feature to squash and merge when you press the green button to merge PR.

example of what I mean about force-pushes:

[MatrixCrawler]

I will try to rebase less during the review :)

[yermulnik]

I will try to rebase less during the review :)

Thanks.
Though please take into consideration whet I wrote: there's actually no need to do that in most of the cases in current conditions 😺 The only meaningful time to force-push is right before you call for review.

[crablab]

LGTM - Warren gave a 👍 in the comments, I believe.

Thanks @MatrixCrawler for splitting the PR :)