Skip to content
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

feat(platform/bitbucket): use development branching model as default branch #20803

Closed

Conversation

setchy
Copy link
Collaborator

@setchy setchy commented Mar 8, 2023

Changes

Updates the Bitbucket Cloud repository initialization logic to fetch and set the development branch name instead of relying only on the main branch name.

Context

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

RahulGautamSingh and others added 19 commits March 4, 2023 06:29
…ebot#19942)

Changes `rangeStrategy` default value from `'replace'` to `'auto'`.

Changes `auto` behavior so that `update-lockfile` is preferred if the manager supports the `updateLockedDependency()` function.

Closes renovatebot#19800

BREAKING CHANGE: Renovate will now default to updating locked dependency versions. To revert to previous behavior, configure rangeStrategy=replace.
…novatebot#19958)

Sets new defaults:
- `prConcurrentLimit`: 10 (instead of 0)
- `prHourlyLimit`: 2 (instead of 0)

Closes renovatebot#19800

BREAKING CHANGE: Renovate now defaults to applying hourly and concurrent PR limits. To revert to unlimited, configure them back to `0`.
Set default GOPROXY value to match `go`'s own default.

Closes renovatebot#20040

BREAKING CHANGE: Renovate will now use go's default `GOPROXY` settings. To avoid using the public proxy, configure `GOPROXY=direct`.
Checks file cache for expired items at the end of a run. Non-breaking change but it may result in some long cleanup jobs for any bots which have been left to populate their package cache for a long time.

Closes renovatebot#13732
…ebot#20150)

Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
…git tag, and preserve existing digest semantics as separate datasource (renovatebot#20178)

Co-authored-by: RahulGautamSingh <rahultesnik@gmail.com>
Co-authored-by: Rhys Arkins <rhys@arkins.net>
Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
Removes "includeForks" option and replaces with "forkProcessing". New default behavior is to process forks if automerge=false.

Closes renovatebot#20752

BREAKING CHANGE: Forked repos will now be processed automatically if autodiscover=false. includeForks is removed and replaced by new option forkProcessing.
Copy link
Collaborator

@rarkins rarkins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please mark as breaking and target v35 branch

@setchy setchy added the breaking Breaking change, requires major version bump label Mar 8, 2023
@setchy
Copy link
Collaborator Author

setchy commented Mar 8, 2023

Please mark as breaking and target v35 branch

Sure - can do.

Will add a few more test cases also

@setchy setchy marked this pull request as draft March 8, 2023 05:24
@setchy setchy changed the base branch from main to v35 March 8, 2023 05:24
@setchy setchy marked this pull request as ready for review March 8, 2023 05:34
RahulGautamSingh and others added 3 commits March 8, 2023 06:34
…ebot#19942)

Changes `rangeStrategy` default value from `'replace'` to `'auto'`.

Changes `auto` behavior so that `update-lockfile` is preferred if the manager supports the `updateLockedDependency()` function.

Closes renovatebot#19800

BREAKING CHANGE: Renovate will now default to updating locked dependency versions. To revert to previous behavior, configure rangeStrategy=replace.
…novatebot#19958)

Sets new defaults:
- `prConcurrentLimit`: 10 (instead of 0)
- `prHourlyLimit`: 2 (instead of 0)

Closes renovatebot#19800

BREAKING CHANGE: Renovate now defaults to applying hourly and concurrent PR limits. To revert to unlimited, configure them back to `0`.
@setchy
Copy link
Collaborator Author

setchy commented Mar 8, 2023

Blocked by #20800

I see #20800 and #20811 as being related to this change, but not blocking this change.

I'd like to propose this feature request moves forward as it has benefits for any new PRs and there are a few manual workarounds teams can use (or currently use) to correct existing PRs, such as

  • manually updating the open PR to target their develop branch
  • rename the Bitbucket PR, close it and then let Renovate raise a new one with the correct target branch during the next cycle

@setchy
Copy link
Collaborator Author

setchy commented Mar 8, 2023

this is a breaking change, we should disable new behavior with a repo config option.

was able to make this a non-breaking change by adding the bbUseDevelopmentBranch config option and defaulting it to false.

@rarkins - with this in place, is it still OK to target this PR to v35?

@setchy setchy marked this pull request as ready for review March 8, 2023 22:26
@setchy setchy requested review from rarkins and viceice March 8, 2023 22:28
@viceice
Copy link
Member

viceice commented Mar 9, 2023

this is a breaking change, we should disable new behavior with a repo config option.

was able to make this a non-breaking change by adding the bbUseDevelopmentBranch config option and defaulting it to false.

@rarkins - with this in place, is it still OK to target this PR to v35?

you can target main when it's not breaking.

do you plan to support more branching models? so this config option should be a enum with null being disabled / current behavior ?

@setchy
Copy link
Collaborator Author

setchy commented Mar 9, 2023

do you plan to support more branching models? so this config option should be a enum with null being disabled / current behavior ?

Can you please explain a bit more about what you mean by "more branching models"?

Development branch is Atlassian Bitbucket terminology and can be configured to any branch. Examples below on how this could be configured by each repository admin

Screenshot 2023-03-09 at 2 21 29 PM
Screenshot 2023-03-09 at 2 23 25 PM
Screenshot 2023-03-09 at 2 23 07 PM
Screenshot 2023-03-09 at 2 24 25 PM

@setchy setchy changed the base branch from v35 to main March 9, 2023 23:21
@setchy setchy changed the base branch from main to v35 March 9, 2023 23:21
@rarkins rarkins force-pushed the v35 branch 4 times, most recently from 181a4d7 to a4ab452 Compare March 10, 2023 08:34
@rarkins rarkins deleted the branch renovatebot:v35 March 10, 2023 09:53
@rarkins rarkins closed this Mar 10, 2023
@rarkins
Copy link
Collaborator

rarkins commented Mar 10, 2023

Sorry this was closed unintentionally by GitHub when v35 was closed

@setchy
Copy link
Collaborator Author

setchy commented Mar 10, 2023

Sorry this was closed unintentionally by GitHub when v35 was closed

All good. Will re-open a new PR to continue the discussion

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 10, 2023
@setchy setchy deleted the feature/bitbucket-development-branch branch April 18, 2023 12:40
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
platform:bitbucket Bitbucket Cloud platform
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bitbucket Cloud: initialize repos with development branch
6 participants