@olblak if you want to set-up a repo in bitbucket that you control, I'm happy to update the e2e tests to use that instead.

Ho nice

Bitbucket doesn't support any HTML in PR descriptions, so I had to add Markdown only views. There's a potential the format could be improved going forward

It's unfortunate because using HTML allows Updatecli to store information in

It's unfortunate because using HTML allows Updatecli to store information in
so it can detect when a pullrequest body needs to be updated.

Yeah I've started using Bitbucket in my new role, its not my favourite user experience.

It also doesn't support HTML comments so we couldn't get clever with hiding information in them either.

@mcwarman I just open a pullrequest on your fork, to update the e2e tests
mcwarman#1

Apparently, I already created a Bitbucket account, and we can have up to 5 people on that workspace

I just tested this pullrequest and it seems to work great 🎉

https://bitbucket.org/updatecli/updatecli/pull-requests/2

Could I ask to also add a documentation page to the website next to https://github.com/updatecli/website/tree/master/content/en/docs/plugins/scm

I don't have access to see that repo on bitbucket (if you added mcwarman that's an old work account I can't get back the username for mcwarman1 is now me).

I'll add the docs for using it.

We either need to make the test repo public, or set BITBUCKET_TOKEN for the e2e generated from the repo:

Ref: https://support.atlassian.com/bitbucket-cloud/docs/access-tokens/

We either need to make the test repo public, or set BITBUCKET_TOKEN for the e2e generated from the repo:

Ref: https://support.atlassian.com/bitbucket-cloud/docs/access-tokens/

Well I thought it already made it public, I'll check that later