-
-
Notifications
You must be signed in to change notification settings - Fork 44
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #181 from twindb/docs-refresh
Docs refresh
- Loading branch information
Showing
16 changed files
with
366 additions
and
195 deletions.
There are no files selected for viewing
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,5 +1,4 @@ | ||
* TwinDB Backup version: | ||
* Python version: | ||
* Operating System: | ||
|
||
### Description | ||
|
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,13 +1,5 @@ | ||
======= | ||
Credits | ||
======= | ||
|
||
Development Lead | ||
---------------- | ||
|
||
* TwinDB Development Team <[email protected]> | ||
|
||
Contributors | ||
------------ | ||
|
||
None yet. Why not be the first? | ||
Aleksandr Kuzminsky <[email protected]> |
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 |
---|---|---|
|
@@ -21,6 +21,7 @@ If you are reporting a bug, please include: | |
|
||
* Your operating system name and version. | ||
* Any details about your local setup that might be helpful in troubleshooting. | ||
It is helpful if you post stack traces and a tool output with the ``--debug`` option. | ||
* Detailed steps to reproduce the bug. | ||
|
||
Fix Bugs | ||
|
@@ -38,7 +39,7 @@ and "help wanted" is open to whoever wants to implement it. | |
Write Documentation | ||
~~~~~~~~~~~~~~~~~~~ | ||
|
||
TwinDB Backup could always use more documentation, whether as part of the | ||
**TwinDB Backup** could always use more documentation, whether as part of the | ||
official TwinDB Backup docs, in docstrings, or even on the web in blog posts, | ||
articles, and such. | ||
|
||
|
@@ -60,29 +61,39 @@ Get Started! | |
Ready to contribute? Here's how to set up TwinDB Backup for local development. | ||
|
||
1. Fork the TwinDB Backup repo on GitHub. | ||
2. Clone your fork locally:: | ||
2. Clone your fork locally: | ||
|
||
.. code-block:: console | ||
$ git clone [email protected]:your_name_here/backup.git twindb_backup | ||
3. Install your local copy into a virtualenv:: | ||
3. Install your local copy into a virtualenv: | ||
|
||
.. code-block:: console | ||
$ make virtualenv | ||
$ source env/bin/activate | ||
$ make bootstrap | ||
4. Create a branch for local development:: | ||
4. Create a branch for local development: | ||
|
||
.. code-block:: console | ||
$ git checkout -b name-of-your-bugfix-or-feature | ||
Now you can make your changes locally. | ||
Now you can make your changes locally. | ||
|
||
5. When you're done making changes, check that your changes pass lint and the tests: | ||
|
||
.. code-block:: console | ||
5. When you're done making changes, check that your changes pass flake8 and the tests, including testing other Python versions with tox:: | ||
$ make lint | ||
$ make test | ||
$ make test-all | ||
To get flake8 and tox, just pip install them into your virtualenv. | ||
6. Commit your changes and push your branch to GitHub: | ||
|
||
6. Commit your changes and push your branch to GitHub:: | ||
.. code-block:: console | ||
$ git add . | ||
$ git commit -m "Your detailed description of your changes." | ||
|
@@ -96,6 +107,7 @@ Pull Request Guidelines | |
Before you submit a pull request, check that it meets these guidelines: | ||
|
||
- The pull request should include tests. | ||
- If the pull request adds functionality, the docs should be updated. Put your new functionality into a function with a docstring, and add the feature to the list in README.rst. | ||
- The pull request should work for Python 2.6 and 2.7. | ||
- Check https://travis-ci.org/twindb/backup/pull_requests and make sure that the tests pass for all supported Python versions. | ||
- If the pull request adds functionality, the docs should be updated. | ||
Put your new functionality into a function with a docstring, and add the feature to the list in ``README.rst``. | ||
- The pull request should work for Python 2.7. | ||
- Check https://travis-ci.com/twindb/backup/pull_requests and make sure that the tests pass. |
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
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.