You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 10, 2019. It is now read-only.
Brief description of what this PR does, and why it is needed.
4
+
5
+
### Checklist
6
+
7
+
-[ ] Description of PR is in an appropriate section of the [changelog](https://github.com/raster-foundry/raster-foundry-python-client/blob/develop/CHANGELOG.rst) and grouped with similar changes if possible
8
+
9
+
### Demo
10
+
11
+
Optional. Screenshots, `curl` examples, etc.
12
+
13
+
### Notes
14
+
15
+
Optional. Ancillary topics, caveats, alternative strategies that didn't work out, anything else.
16
+
17
+
18
+
## Testing Instructions
19
+
20
+
* How to test this PR
21
+
* Prefer bulleted description
22
+
* Start after checking out this branch
23
+
* Include any setup required, such as bundling scripts, restarting services, etc.
Copy file name to clipboardExpand all lines: README.rst
-34
Original file line number
Diff line number
Diff line change
@@ -70,37 +70,3 @@ The test suite execution process is managed by ``tox``:
70
70
.. code:: bash
71
71
72
72
$ tox
73
-
74
-
75
-
Releases
76
-
--------
77
-
78
-
Releases are automatically published to PyPI through Travis CI when commits are tagged. The following ``git flow`` commands lead to a tagged commit that can be pushed to GitHub:
79
-
80
-
81
-
.. code:: bash
82
-
83
-
$ git flow release start X.Y.Z
84
-
$ docker run -ti --rm -v "${PWD}:/changelog" -w "/changelog""quay.io/azavea/github-changelog-generator:v1.14.3" \
85
-
--token "${GITHUB_TOKEN}" \
86
-
--future-release "X.Y.Z" \
87
-
--no-issues \
88
-
--no-author \
89
-
--release-branch develop
90
-
$ pandoc CHANGELOG.md -o CHANGELOG.rst
91
-
$ rm CHANGELOG.md
92
-
$ vim setup.py
93
-
$ git commit -m "X.Y.Z"
94
-
$ git flow release publish X.Y.Z
95
-
$ git flow release finish X.Y.Z
96
-
97
-
98
-
After you've completed the ``git flow`` steps above, you'll need to push the changes from your local repository to the GitHub repository:
0 commit comments