atomic-threat-coverage/CONTRIBUTING.md

32 lines
2.4 KiB
Markdown
Raw Permalink Normal View History

2019-01-15 16:44:04 +00:00
# How to submit an issue?
2019-01-09 22:13:49 +00:00
2019-02-10 19:50:01 +00:00
First, please refer to [contribution-guide.org](http://www.contribution-guide.org/) for the steps we expect from contributors before submitting an issue or bug report. Be as concrete as possible, include relevant logs, package versions etc.
2019-01-09 22:13:49 +00:00
2019-08-12 21:20:30 +00:00
Also, please check our [FAQ](https://github.com/atc-project/atomic-threat-coverage#faq).
2019-01-09 22:07:42 +00:00
2020-04-17 00:46:52 +00:00
The proper place for open-ended questions is [Slack](https://join.slack.com/t/atomicthreatcoverage/shared_invite/zt-6ropl01z-wIdiq3M0AEZPj_HiKfbiBg) or [Telegram](https://t.me/atomic_threat_coverage).
2019-01-09 22:07:42 +00:00
2019-01-15 16:44:04 +00:00
# How to add a new feature or create a pull request?
2019-08-12 21:20:30 +00:00
1. Fork the [ATC repository](https://github.com/atc-project/atomic-threat-coverage)
2019-01-15 16:44:04 +00:00
2. Clone your fork: `git clone git clone https://gitlab.com/<YOUR GITLAB USERNAME>/atomic-threat-coverage.git`
3. Create a new branch based on `develop`: `git checkout -b my-feature develop`
4. Setup your Python enviroment
- Create a new [virtual environment](https://virtualenv.pypa.io/en/stable/): `pip install virtualenv; virtualenv atc_env` and activate it:
- For linux: `source atc_env/bin/activate`
- For windows: `atc_env\Scripts\activate`
2019-01-21 11:24:23 +00:00
- Install ATC and its test dependencies in [editable mode](https://pip.pypa.io/en/stable/reference/pip_install/#editable-installs):
2019-01-15 16:44:04 +00:00
- For linux: `pip install -r requirements.txt`
- For windows: `pip install -r requirements.txt`
5. Implement your changes
2019-02-10 19:50:01 +00:00
6. Check your code for PEP8 requirements
2019-01-15 16:44:04 +00:00
7. Add files, commit and push: `git add ... ; git commit -m "my commit message"; git push origin my-feature`
8. [Create a PR](https://help.github.com/articles/creating-a-pull-request/) on Github. Write a **clear description** for your PR, including all the context and relevant information, such as:
- The issue that you fixed, e.g. `Fixes #123`
- Motivation: why did you create this PR? What functionality did you set out to improve? What was the problem + an overview of how you fixed it? Whom does it affect and how should people use it?
- Any other useful information: links to other related Github or mailing list issues and discussions, benchmark graphs, academic papers…
2019-02-28 21:29:36 +00:00
- Note that your Pull Request should be into **develop** branch, **not master**
2019-01-15 16:44:04 +00:00
2019-08-12 21:20:30 +00:00
<!-- P.S. for developers: see our [Developer Page](https://github.com/atc-project/atomic-threat-coverage/wikis/Developer-guide) for details on the code style, CI, testing and similar. -->
2019-01-15 16:44:04 +00:00
**Thanks and let's improve the open source world together!**