Skip to content
This repository was archived by the owner on Aug 28, 2021. It is now read-only.

Commit 6266c38

Browse files
committed
2 parents 993edff + 31fa2bf commit 6266c38

File tree

2 files changed

+44
-0
lines changed

2 files changed

+44
-0
lines changed

CHANGELOG.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
## [v1.0.26]() (23/01/2021) 🚀
2+
Fix some bugs in the readme and add some informational files.

CONTRIBUTING.md

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
# Contributing
2+
We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
3+
4+
- Reporting a bug
5+
- Discussing the current state of the code
6+
- Submitting a fix
7+
- Proposing new features
8+
- Becoming a maintainer
9+
10+
## We Develop with Github
11+
We use github to host code, to track issues and feature requests, as well as accept pull requests.
12+
13+
## We Use [Github Flow](https://guides.github.com/introduction/flow/index.html), So All Code Changes Happen Through Pull Requests
14+
Pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests:
15+
16+
1. Fork the repo and create your branch from `master`.
17+
2. If you've added code that should be tested, add tests.
18+
3. Ensure the test suite passes.
19+
4. Make sure your code lints.
20+
5. Issue that pull request!
21+
22+
## Any contributions you make will be under the MIT Software License
23+
In short, when you submit code changes, your submissions are understood to be under the same [MIT License](http://choosealicense.com/licenses/mit/) that covers the project. Feel free to contact the maintainers if that's a concern.
24+
25+
## Report bugs using Github's [issues](https://github.com/briandk/transcriptase-atom/issues)
26+
We use GitHub issues to track public bugs. Report a bug by [opening a new issue](https://github.com/EliazBobadilla/Python-UltiSnippets-VSCode-Extension/issues) it's that easy!
27+
28+
29+
**Great Bug Reports** tend to have:
30+
31+
- A quick summary and/or background
32+
- Steps to reproduce
33+
- Be specific!
34+
- Give sample code if you can.
35+
- What you expected would happen
36+
- What actually happens
37+
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
38+
39+
People *love* thorough bug reports. I'm not even kidding.
40+
41+
## License
42+
By contributing, you agree that your contributions will be licensed under its MIT License.For more information read [here](https://github.com/EliazBobadilla/Python-UltiSnippets-VSCode-Extension/blob/main/LICENSE).

0 commit comments

Comments
 (0)