Skip to content

Commit

Permalink
Fix typos, style improvements in CONTRIBUTING.md
Browse files Browse the repository at this point in the history
  • Loading branch information
myabc authored Oct 7, 2024
1 parent d4d2057 commit 22aff4d
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ We are pleased that you are thinking about contributing to OpenProject! This gui

## Get in touch

Please get in touch with us using our [develompment forum](https://community.openproject.org/projects/openproject/boards/7) or send us an email to [email protected].
Please get in touch with us using our [development forum](https://community.openproject.org/projects/openproject/boards/7) or send us an email to [email protected].

## Issue tracking and coordination

Expand Down Expand Up @@ -61,7 +61,7 @@ git push origin <your feature branch>

- Create a pull request against a branch of of the <opf/openproject> repository, containing a ***clear description*** of what the pull request attempts to change and/or fix.

If your pull request **does not contain a description** for what it does and what it's intentions are,
If your pull request **does not contain a description** for what it does and what its intentions are,
we will reject it.
If you are working on a specific work package from the [list](https://community.openproject.org/projects/openproject/work_packages),
you may include a link to that work package in the description, so we can track your work.
Expand Down Expand Up @@ -100,11 +100,11 @@ A fix for the current version (called "Hotfix" and the branch ideally being name
should target `release/*` and a fix for the former version
(called "Backport" and the branch ideally being named `backport/XYZ`)
should target `backport/*`. We will try to merge hotfixes into dev branch
but if that is no trivial task, we might ask you to create another PR for that.
but if that is a non-trivial task, we might ask you to create another PR for that.

## Inactive pull requests

We want to keep the Pull request list as cleaned up as possible - we will aim close pull requests
We want to keep the Pull request list as tidy as possible - we will aim close pull requests
after an **inactivity period of 30 days** (no comments, no further pushes)
which are not labelled as `work in progress` by us.

Expand Down

0 comments on commit 22aff4d

Please sign in to comment.