Skip to content

Latest commit

 

History

History
101 lines (60 loc) · 4.13 KB

CONTRIBUTING.md

File metadata and controls

101 lines (60 loc) · 4.13 KB
Raw

Contributing to validate-python-headers

Everything you need to know to contribute efficiently to the project!

Whatever the way you wish to contribute to the project, please respect the code of conduct.

Codebase structure

  • ./src - The actual script used for header verification
  • action.yml - The marketplace action configuration file
  • Dockerfile - The dockerfile of the action
  • entrypoint.sh - The bash script executed by the Docker container

Continuous Integration

This project uses the following integrations to ensure proper codebase maintenance:

  • Github Worklow - run jobs for package build and coverage
  • Codacy - analyzes commits for code quality

As a contributor, you will only have to ensure coverage of your code by adding appropriate unit testing of your code.

Feedback

Feature requests & bug report

Whether you encountered a problem, or you have a feature suggestion, your input has value and can be used by contributors to reference it in their developments. For this purpose, we advise you to use Github issues.

First, check whether the topic wasn't already covered in an open / closed issue. If not, feel free to open a new one! When doing so, use issue templates whenever possible and provide enough information for other contributors to jump in.

Questions

If you are wondering how to do something with this action, or a more general question, you should consider checking out Github discussions. See it as a Q&A forum, or the project-specific StackOverflow!

Submitting a Pull Request

Preparing your local branch

1 - Fork this repository by clicking on the "Fork" button at the top right of the page. This will create a copy of the project under your GitHub account (cf. Fork a repo).

2 - Clone your fork to your local disk and set the upstream to this repo

git clone [email protected]:<YOUR_GITHUB_ACCOUNT>/validate-python-headers.git
cd validate-python-headers
git remote add upstream https://github.com/frgfm/validate-python-headers.git

3 - You should not work on the main branch, so let's create a new one

git checkout -b a-short-description

4 - You only have to set your development environment now, using the following command:

make build

Developing your feature

Commits

  • Code: ensure to provide docstrings to your Python code. In doing so, please follow Google-style so it can ease the process of documentation later.
  • Commit message: please follow Udacity guide

Action sanity check

In order to run the same checks as the CI workflows, you can run tests locally:

make test

Code quality

To run all quality checks together

make quality

The previous command won't modify anything in your codebase. Some fixes (import ordering and code formatting) can be done automatically using the following command:

make style

Submit your modifications

Push your last modifications to your remote branch

git push -u origin a-short-description

Then open a Pull Request from your fork's branch. Follow the instructions of the Pull Request template and then click on "Create a pull request".