Skip to content

Add links to CONTRIBUTING and onboarding, align content with these. #267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
poshul wants to merge 2 commits into
base: develop
Choose a base branch
from
Open

Add links to CONTRIBUTING and onboarding, align content with these. #267

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2013028
Add links to CONTRIBUTING and onboarding, align content with these.
poshul Mar 11, 2026
ef4a99a
Fix Contributor Onboarding Guide link
poshul Mar 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 8 additions & 13 deletions docs/manual/develop.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,12 @@ To contribute to OpenMS:

For any questions, please [contact us](/about/communication.md).

**New to the project?** Start with our [Contributor Onboarding Guide](https://openms.de/contribute) to understand project structure and communication channels.

**Ready to contribute code?** See [CONTRIBUTING.md](https://github.com/OpenMS/OpenMS/blob/develop/CONTRIBUTING.md) for workflow and process guidelines.

This guide covers technical details for active developers.

## Technical documentation

```{note}
Expand All @@ -22,20 +28,9 @@ See the documentation for the [latest release](https://abibuilder.cs.uni-tuebing

## Contribution guidelines

Before contributing to OpenMS, read information on the development model and conventions followed to maintain a coherent
code base.

### Development model

OpenMS follows the [Gitflow development workflow](http://nvie.com/posts/a-successful-git-branching-model/).

Every contributor is encouraged to create their own fork (even if they are eligible to push directly to OpenMS).
To create a fork:
For detailed contribution workflows, pull request checklists, issue reporting guidelines, and OpenMS-specific development processes, see the canonical [CONTRIBUTING.md](https://github.com/OpenMS/OpenMS/blob/develop/CONTRIBUTING.md) in the main repository.

1. Follow the documentation on [forking](https://help.github.com/articles/fork-a-repo).
2. Keep your fork [up-to-date](https://help.github.com/articles/syncing-a-fork).
3. Create a [pull request](https://help.github.com/articles/using-pull-requests). Before opening the pull request, please
view the [pull request guidelines](/manual/contribute/pull-request-checklist.md).
This developer guide focuses on technical implementation details below.

### Coding conventions

Expand Down
Loading