This repository was archived by the owner on Mar 6, 2026. It is now read-only.
chore: disable required linear history on v3 branch#1018
Merged
gcf-merge-on-green[bot] merged 5 commits intomainfrom Oct 12, 2021
Merged
chore: disable required linear history on v3 branch#1018gcf-merge-on-green[bot] merged 5 commits intomainfrom
gcf-merge-on-green[bot] merged 5 commits intomainfrom
Conversation
This should prevent conflicts when we sync v3 with main.
product-auto-label
Bot
added
the
api: bigquery
google-cla
Bot
added
the
cla: yes
Contributor
Author
|
Seems I got the schema wrong. I was guessing the property based on required_linear_history here: https://docs.github.com/en/rest/reference/repos#update-branch-protection |
tswast
added
the
do not merge
tseaver
approved these changes
Oct 12, 2021
Contributor
|
@tswast There's an example config with comments on all the possible options in the bot README: https://github.com/googleapis/repo-automation-bots/tree/main/packages/sync-repo-settings
|
Contributor
Author
|
Hmmm... Looks like sync-repo-settings config doesn't allow a per-branch setting for
I think I need both. |
tswast
added
automerge
gcf-merge-on-green
Bot
removed
the
automerge
abdelmegahedgoogle
pushed a commit
to abdelmegahedgoogle/python-bigquery
that referenced
this pull request
Apr 17, 2023
This should prevent conflicts when we sync v3 with main. Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly: - [ ] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/python-bigquery/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [ ] Ensure the tests and linter pass - [ ] Code coverage does not decrease (if any source code was changed) - [ ] Appropriate docs were updated (if necessary)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This should prevent conflicts when we sync v3 with main.
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly: