-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding bitbucket cloud support #479
Changes from 35 commits
3d51a03
ed6e44b
ecbbfc2
08e2f99
f9d80fb
0cf3f8b
ce8d671
c6d00fe
0037e33
7e4e678
4da8faf
1e99218
bca67e4
c20dfb5
3247873
0c42004
3340226
529ce19
1013cba
cf69583
0a80442
97d129b
471bfb9
6db683c
1f94161
080287c
5046599
0a683fe
1d5a2c2
73c5ee3
6e09ef6
b8d121a
b7aa28a
8c14b0f
2432aa3
ca93a8f
5c7bdef
e122da6
e799052
ce58a71
7a8fb81
16e4493
f84981a
9928e39
6fbd56c
e1bdb9b
a3125c3
de1ec4a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -132,3 +132,27 @@ All configuration in multi-gitter can be done through command line flags, config | |
{{end}}{{end}} | ||
|
||
Do you have a nice script that might be useful to others? Please create a PR that adds it to the [examples folder](/examples). | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @lindell we added a section here in the README to document how to use bitbucket cloud and the limitations as well as links to official documentation. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think the documentation look good. But it is a bit too much to have in the main readme. We could either:
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. done, comments added about beta support and documented any issues/missing features |
||
## Bitbucket Cloud | ||
|
||
In order to use bitbucket cloud you will need to create and use an [App Password](https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/). The app password you create needs sufficient permissions so ensure you grant it Read and Write access to projects, repositories and pull requests and at least Read access to your account and workspace membership. | ||
|
||
You will need to configure the bitbucket workspace using the `org` option for multi-gitter for the repositories you want to make changes to e.g. `multi-gitter run examples/go/upgrade-go-version.sh -u your_username --org "your_workspace"` | ||
|
||
### Example | ||
Here is an example of using the command line options to run a script from the `examples/` directory and make pull-requests for a few repositories in a specified workspace. | ||
```shell | ||
export BITBUCKET_CLOUD_APP_PASSWORD="your_app_password" | ||
multi-gitter run examples/go/upgrade-go-version.sh -u your_username --org "your_workspace" --repo "your_first_repository,your_second_repository" --platform bitbucket_cloud -m "your_commit_message" -B your_branch_name | ||
``` | ||
|
||
### Bitbucket Cloud Limitations | ||
Currently, we add the repositories default reviewers as a reviewer for any pull-request you create. If you want to specify specific reviewers, you will need to add them using their `UUID` instead of their username since bitbucket does not allow us to look up a `UUID` using their username. [This article has more information about where you can get a users UUID.](https://community.atlassian.com/t5/Bitbucket-articles/Retrieve-the-Atlassian-Account-ID-AAID-in-bitbucket-org/ba-p/2471787) | ||
|
||
We don't support specifying specific projects for bitbucket cloud yet, you should still be able to make changes to the repositories you want but certain functionality, like forking, does not work as well until we implement that feature. | ||
Using `fork: true` is currently experimental within multi-gitter for Bitbucket Cloud, and will be addressed in future updates. | ||
Here are the known limitations: | ||
- The forked repository will appear in the user-provided workspace/orgName, with the given repo name, but will appear in a random project within that workspace. | ||
- Using `git-type: cmd` is required for Bitbucket Cloud forking for now until better support is added, as `git-type: go` causes inconsistent behavior(intermittent unauthorized errors). | ||
|
||
We also only support modifying a single workspace, any additional workspaces passed into the multi-gitter `org` option will be ignored after the first value. |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,5 +2,5 @@ | |
|
||
# Title: Upgrade Go version in go modules | ||
|
||
go mod edit -go 1.18 | ||
go mod edit -go 1.19 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We changed this for testing, we'll switch it back There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ping on this comment |
||
go mod tidy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove