mirror of https://github.com/soywod/himalaya.git synced 2024-11-22 02:50:19 +00:00

* update main screenshot readme

* add contributing file

* update changelog

* doc: remove roadmap from reame

* improve main comments

* improve arg and handler logs

* fix multiple recipients issue (#288)

* add notify-query config option (#289)

* set up end-to-end encryption (#287)

* init basic pgp encrypt/decrypt

* add small rpgp poc for (#286)

* improve decrypt parts logs

* add pgp-decrypt-cmd to config

* add pgp-encrypt-cmd to config

* init pgp signature

* improve decrypt part readability

* improve encrypt multipart, remove sign

* remove unused md5 lib

* add encrypt arg to reply and forward commands

* fix typos

* prepare v0.5.5

2022-02-08 14:50:09 +01:00

2 KiB

Raw Blame History

Himalaya contributing guide

Thank you for investing your time in contributing to Himalaya!

In this guide you will get an overview of the contribution workflow from opening an issue, creating a PR, reviewing, and merging the PR.

New contributor guide

To get an overview of the project, read the README. To get more information about the project, read the wiki.

Getting started

Issues

Create a new issue

If you spot a problem with the docs, search if an issue already exists. If a related issue doesn't exist, you can open a new issue using a relevant issue form.

Solve an issue

Scan through our existing issues to find one that interests you. You can narrow down the search using labels as filters. If you find an issue to work on, you are welcome to open a PR with a fix.

Make Changes

Make changes in the UI

Click Make a contribution at the bottom of any docs page to make small changes such as a typo, sentence fix, or a broken link. This takes you to the .md file where you can make your changes and create a pull request for a review.

Make changes locally

First, follow the instructions on how to install Himalaya from sources. Then, create a working branch and start with your changes!

Commit your update

Commit the changes once you are happy with them. Commit messages follow the Angular Convention, but contain only a subject. The subject can be prefixed with a custom context like msg: , mbox: , imap: etc.

Use imperative, present tense: “change” not “changed” nor “changes”
Don't capitalize first letter
No dot (.) at the end

Pull Request

When you're finished with the changes, create a pull request, also known as a PR.

2 KiB Raw Blame History