Skip to content

Latest commit

 

History

History
32 lines (21 loc) · 1.35 KB

CONTRIBUTING.md

File metadata and controls

32 lines (21 loc) · 1.35 KB

Contributing to process-snapshots-toolkit

The process-snapshots-toolkit project team welcomes contributions from the community. Before you start working with process-snapshots-toolkit, please read our Developer Certificate of Origin. All contributions to this repository must be signed as described on that page. Your signature certifies that you wrote the patch or have the right to pass it on as an open-source patch.

What should I know before I get started?

Good understanding of Ghidra internals and how to use it as command line tool.

Understanding of Windows memory layout and PE format.

How Can I Contribute?

  • Report/Fix bugs
  • Suggest/Implement enhancements

Contribution Process

Follow the GitHub process

Code Style

Python - PEP8 standards: https://pypi.python.org/pypi/pep8

Before commiting the code, please run pylint.sh and black.sh to check for errors/warning and correct code formatting.

Formatting Commit Messages

We follow the conventions on How to Write a Git Commit Message.

Be sure to include any related GitHub issue references in the commit message. See GFM syntax for referencing issues and commits.