Skip to content
Snippets Groups Projects
Select Git revision
  • EWM10343_ragged_workspace_write_slab_segfault
  • main default
  • 39088_short_form_spacegroups
  • pin_conda_in_packaging_env
  • 39013-highlight-bool-keywords-in-script-editor
  • pin_cmake_less_than_4
  • rework_legacy_napi
  • cppcheck_fixes
  • ewm10069-DetermineGaugeVolume
  • alma9-test-pipeline
  • abs-corr-raster-gauge-volume-check-shape
  • 38301-unpin-mkl
  • bayes_quasi_test_tolerance
  • hb2a_merge_fix
  • update-snap-idf
  • 38668_disable_unsupported_Rietveld_from_diffraction_interface
  • getting_started_mantid_developer_update_info
  • convertunits
  • ewm9983_deprecate_unwrapsns
  • 38968_expose_fitting_params
  • v6.12.20250324.1657
  • v6.12.0.1
  • v6.12.20250321.0927
  • v6.12.20250320.1713
  • v6.12.0.1rc3
  • v6.12.20250314.1925
  • v6.12.0.1rc2
  • v6.12.20250313.1634
  • v6.12.20250312.2000
  • v6.12.0.1rc1
  • v6.12.20250310.1545
  • v6.12.20250306.2035
  • v6.12.20250304.2007
  • v6.12.20250303.2021
  • v6.12.20250228.2045
  • v6.11.0.5
  • v6.12.0
  • v6.11.0.5rc1
  • v6.11.20250220.1815
  • v6.11.20250218.1111
40 results
Blame Permalink
Code owners
Assign users and groups as approvers for specific file changes. Learn more.
After you've reviewed these contribution guidelines, you'll be all set to contribute to this project.
CONTRIBUTING.md 904 B

The developer documentation has information on how to participate in the mantid project as a developer. This document is meant to outline the steps for contributing to mantid without becomming a developer.

  1. Fork the repository.
  2. Make changes as you see fit. Please still follow the guidelines for running the unit tests and the build servers.
  3. Submit a pull request. Pull requests work best if you do your work on a branch rather than in the master.
  4. Email mantid-help@mantidproject.org as an extra poke to get people to notice your change. The mantid project does not use pull requests internally so the extra notification makes sure that people notice the request.