-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore: rename package to google-cloud-dataflow-client (#4)
* chore: rename package to google-cloud-dataflow-client * 🦉 Updates from OwlBot See https://github.com/googleapis/repo-automation-bots/blob/master/packages/owl-bot/README.md * chore: add license header to .Owlbot.lock.yaml Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
- Loading branch information
1 parent
79d33e7
commit 7653220
Showing
24 changed files
with
83 additions
and
69 deletions.
There are no files selected for viewing
14 changes: 14 additions & 0 deletions
14
packages/google-cloud-dataflow-client/.github/.OwlBot.lock.yaml
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,17 @@ | ||
# Copyright 2021 Google LLC | ||
# | ||
# Licensed under the Apache License, Version 2.0 (the "License"); | ||
# you may not use this file except in compliance with the License. | ||
# You may obtain a copy of the License at | ||
# | ||
# http://www.apache.org/licenses/LICENSE-2.0 | ||
# | ||
# Unless required by applicable law or agreed to in writing, software | ||
# distributed under the License is distributed on an "AS IS" BASIS, | ||
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
# See the License for the specific language governing permissions and | ||
# limitations under the License. | ||
|
||
docker: | ||
image: gcr.io/repo-automation-bots/owlbot-python:latest | ||
digest: sha256:99d90d097e4a4710cc8658ee0b5b963f4426d0e424819787c3ac1405c9a26719 |
This file contains 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
2 changes: 1 addition & 1 deletion
2
packages/google-cloud-dataflow-client/.github/PULL_REQUEST_TEMPLATE.md
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -35,21 +35,21 @@ Using a Development Checkout | |
You'll have to create a development environment using a Git checkout: | ||
|
||
- While logged into your GitHub account, navigate to the | ||
``python-dataflow`` `repo`_ on GitHub. | ||
``python-dataflow-client`` `repo`_ on GitHub. | ||
|
||
- Fork and clone the ``python-dataflow`` repository to your GitHub account by | ||
- Fork and clone the ``python-dataflow-client`` repository to your GitHub account by | ||
clicking the "Fork" button. | ||
|
||
- Clone your fork of ``python-dataflow`` from your GitHub account to your local | ||
- Clone your fork of ``python-dataflow-client`` from your GitHub account to your local | ||
computer, substituting your account username and specifying the destination | ||
as ``hack-on-python-dataflow``. E.g.:: | ||
as ``hack-on-python-dataflow-client``. E.g.:: | ||
|
||
$ cd ${HOME} | ||
$ git clone [email protected]:USERNAME/python-dataflow.git hack-on-python-dataflow | ||
$ cd hack-on-python-dataflow | ||
# Configure remotes such that you can pull changes from the googleapis/python-dataflow | ||
$ git clone [email protected]:USERNAME/python-dataflow-client.git hack-on-python-dataflow-client | ||
$ cd hack-on-python-dataflow-client | ||
# Configure remotes such that you can pull changes from the googleapis/python-dataflow-client | ||
# repository into your local repository. | ||
$ git remote add upstream [email protected]:googleapis/python-dataflow.git | ||
$ git remote add upstream [email protected]:googleapis/python-dataflow-client.git | ||
# fetch and merge changes from upstream into master | ||
$ git fetch upstream | ||
$ git merge upstream/master | ||
|
@@ -60,7 +60,7 @@ repo, from which you can submit a pull request. | |
To work on the codebase and run the tests, we recommend using ``nox``, | ||
but you can also use a ``virtualenv`` of your own creation. | ||
|
||
.. _repo: https://github.com/googleapis/python-dataflow | ||
.. _repo: https://github.com/googleapis/python-dataflow-client | ||
|
||
Using ``nox`` | ||
============= | ||
|
@@ -113,7 +113,7 @@ Coding Style | |
export GOOGLE_CLOUD_TESTING_BRANCH="master" | ||
|
||
By doing this, you are specifying the location of the most up-to-date | ||
version of ``python-dataflow``. The the suggested remote name ``upstream`` | ||
version of ``python-dataflow-client``. The the suggested remote name ``upstream`` | ||
should point to the official ``googleapis`` checkout and the | ||
the branch should be the main branch on that remote (``master``). | ||
|
||
|
@@ -185,10 +185,10 @@ The `description on PyPI`_ for the project comes directly from the | |
``README``. Due to the reStructuredText (``rst``) parser used by | ||
PyPI, relative links which will work on GitHub (e.g. ``CONTRIBUTING.rst`` | ||
instead of | ||
``https://github.com/googleapis/python-dataflow/blob/master/CONTRIBUTING.rst``) | ||
``https://github.com/googleapis/python-dataflow-client/blob/master/CONTRIBUTING.rst``) | ||
may cause problems creating links or rendering the description. | ||
|
||
.. _description on PyPI: https://pypi.org/project/google-cloud-dataflow | ||
.. _description on PyPI: https://pypi.org/project/google-cloud-dataflow-client | ||
|
||
|
||
************************* | ||
|
@@ -210,7 +210,7 @@ We support: | |
|
||
Supported versions can be found in our ``noxfile.py`` `config`_. | ||
|
||
.. _config: https://github.com/googleapis/python-dataflow/blob/master/noxfile.py | ||
.. _config: https://github.com/googleapis/python-dataflow-client/blob/master/noxfile.py | ||
|
||
|
||
We also explicitly decided to support Python 3 beginning with version 3.6. | ||
|
This file contains 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
This file contains 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
Oops, something went wrong.