fz0x1/Stegano
1
0
Fork 0
mirror of https://github.com/cedricbonhomme/Stegano.git synced 2025-06-28 03:06:14 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Typo.

Browse source
This commit is contained in:
Cédric Bonhomme 2017-01-30 08:23:38 +01:00
parent a65bce640f
commit 4c2570769d
No known key found for this signature in database
GPG key ID: A1CB94DE57B7A70D
1 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

12
CONTRIBUTING.rst
View file

@ -11,9 +11,7 @@ When contributing code, you'll want to follow this checklist:
1. Fork the repository on GitHub.
2. Run the tests to confirm they all pass on your system. If they don't, you'll
need to investigate why they fail. If you're unable to diagnose this
yourself, raise it as a bug report by following the guidelines in this
document: :ref:`bug-reports`.
need to investigate why they fail.
3. Write tests that demonstrate your bug or feature. Ensure that they fail.
4. Make your change.
5. Run the entire test suite again, confirming that all tests pass *including
@ -59,13 +57,15 @@ Questions
The GitHub issue tracker is for *bug reports* and *feature requests*. Please do
not use it to ask questions about how to use Stegano. These questions should
instead be directed to [Stack Overflow](https://stackoverflow.com/). Make sure
instead be directed to Stack Overflow. Make sure
that your question is tagged with the `python-stegano` tag when asking it on
Stack Overflow, to ensure that it is answered promptly and accurately.
You can search for questions with
<these tags `http://stackoverflow.com/questions/tagged/python+steganography`>_.
`these tags <http://stackoverflow.com/questions/tagged/python+steganography>_.
## Good Bug Reports
Good Bug Reports
================
Please be aware of the following things when filing bug reports: