Skip to content
This repository has been archived by the owner on Nov 29, 2023. It is now read-only.

chore: unblacken snippets noxfile #66

Closed
wants to merge 1 commit into from
Closed

Conversation

yoshi-automation
Copy link
Contributor

This PR was generated using Autosynth. 🌈

Synth log will be available here:
https://source.cloud.google.com/results/invocations/008ce5bf-87d6-4df6-a516-9e6d6ecebea4/targets

  • To automatically regenerate this PR, check this box.

        autosynth cannot find the source of changes triggered by earlier changes in this
        repository, or by version upgrades to tools such as linters.
@yoshi-automation yoshi-automation requested a review from a team January 8, 2021 13:53
@yoshi-automation yoshi-automation requested a review from a team as a code owner January 8, 2021 13:53
@google-cla google-cla bot added the cla: yes This human has signed the Contributor License Agreement. label Jan 8, 2021
@product-auto-label product-auto-label bot added the api: bigqueryreservation Issues related to the googleapis/python-bigquery-reservation API. label Jan 8, 2021
@tswast tswast changed the title [CHANGE ME] Re-generated to pick up changes from self. chore: unblacken snippets noxfile Jan 8, 2021
@tswast
Copy link
Contributor

tswast commented Jan 8, 2021

As I said here: https://github.com/googleapis/python-bigquery-reservation/pull/68/files#r554008409

I'm a bit curious as to why the "blacken" gets reverted. We run blacken as the last step here: https://github.com/googleapis/python-bigquery-reservation/blob/master/synth.py#L66

But maybe we need to loop through the samples directories and run those blacken sessions?

@tswast tswast added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Jan 14, 2021
@leahecole
Copy link

Oof, honestly, I'm not sure what's going on under the hood here. My grasp of synthtool magic is minimal. I'm not sure if it means we need to blacken the noxfile template in the synthtool repo itself, or if it's something special here. @busunkim96 might have an opinion here

@tswast
Copy link
Contributor

tswast commented Feb 3, 2021

@leahecole #71 should fix it in the future

gcf-merge-on-green bot pushed a commit that referenced this pull request Feb 3, 2021
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-reservation/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)

Fixes googleapis/synthtool#899 🦕
Closes #66
parthea pushed a commit to googleapis/google-cloud-python that referenced this pull request Sep 22, 2023
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-reservation/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)

Fixes googleapis/synthtool#899 🦕
Closes googleapis/python-bigquery-reservation#66
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
api: bigqueryreservation Issues related to the googleapis/python-bigquery-reservation API. cla: yes This human has signed the Contributor License Agreement. context: none do not merge Indicates a pull request not ready for merge, due to either quality or timing.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants