SWIFTSIM
diff --git a/‎.github/workflows/main.yml‎
Lines changed: 30 additions & 0 deletions b/‎.github/workflows/main.yml‎
Lines changed: 30 additions & 0 deletions
diff --git a/‎.gitignore‎
Lines changed: 4 additions & 0 deletions b/‎.gitignore‎
Lines changed: 4 additions & 0 deletions
diff --git a/‎CONTRIBUTING.md‎
Lines changed: 67 additions & 0 deletions b/‎CONTRIBUTING.md‎
Lines changed: 67 additions & 0 deletions
@@ -0,0 +1,30 @@
+# This is a basic workflow to help you get started with Actions
+
+name: CI
+
+# Controls when the workflow will run
+on:
+  # Triggers the workflow on push or pull request events but only for the master branch
+  push:
+    branches: [ master ]
+  pull_request:
+    branches: [ master ]
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# A workflow run is made up of one or more jobs that can run sequentially or in parallel
+jobs:
+  # Formatting check
+  formatting:
+    # The type of runner that the job will run on
+    runs-on: ubuntu-latest
+
+    # Steps represent a sequence of tasks that will be executed as part of the job
+    steps:
+      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
+      - uses: actions/checkout@v2
+
+      # Runs the formatting script
+      - name: Formatting
+        run: bash format.sh --check
@@ -2,6 +2,8 @@ __pycache__
 *~
 logs
 openmpi-5.0.3-hdf5-1.12.3-env
+black_formatting_env
+*egg-info
 
 documentation/SOAP.aux
 documentation/SOAP.log
@@ -16,3 +18,5 @@ documentation/units.tex
 
 tests/FLAMINGO/test_parameters.yml
 tests/COLIBRE/test_parameters.yml
+tests/test_SO_radius_*.png
+test_data/*
@@ -0,0 +1,67 @@
+Contributing to SOAP
+==========================
+
+Contributions for SOAP should come through our GitHub repository,
+available at https://github.com/swiftsim/SOAP.
+
+Contributions are always welcome, but you should make sure of the following:
+
++ Your contributions pass all unit tests
++ Your contributions add unit tests for new functionality
++ Your contributions are formatted with the `black` formatter (see `format.sh`)
++ Your contributions are documented fully
+
+You should also abide by the following code of conduct:
+
+### Code of Conduct
+
+The community of participants in open source Astronomy projects is made up of
+members from around the globe with a diverse set of skills, personalities,
+and experiences. It is through these differences that our community
+experiences success and continued growth. We expect everyone in our community
+to follow these guidelines when interacting with others both inside and
+outside of our community. Our goal is to keep ours a positive, inclusive,
+successful, and growing community.
+
+As members of the community,
+
++ We pledge to treat all people with respect and provide a harassment- and
+  bullying-free environment, regardless of sex, sexual orientation and/or
+  gender identity, disability, physical appearance, body size, race,
+  nationality, ethnicity, and religion. In particular, sexual language and
+  imagery, sexist, racist, or otherwise exclusionary jokes are not appropriate.
++ We pledge to respect the work of others by recognizing
+  acknowledgement/citation requests of original authors. As authors, we pledge
+  to be explicit about how we want our own work to be cited or acknowledged.
++ We pledge to welcome those interested in joining the community, and realize
+  that including people with a variety of opinions and backgrounds will only
+  serve to enrich our community. In particular, discussions relating to
+  pros/cons of various technologies, programming languages, and so on are
+  welcome, but these should be done with respect, taking proactive measure to
+  ensure that all participants are heard and feel confident that they can
+  freely express their opinions.
++ We pledge to welcome questions and answer them respectfully, paying
+  particular attention to those new to the community. We pledge to provide
+  respectful criticisms and feedback in forums, especially in discussion
+  threads resulting from code contributions.
++ We pledge to be conscientious of the perceptions of the wider community and
+  to respond to criticism respectfully. We will strive to model behaviours that
+  encourage productive debate and disagreement, both within our community and
+  where we are criticized. We will treat those outside our community with the
+  same respect as people within our community.
++ We pledge to help the entire community follow the code of conduct, and to
+  not remain silent when we see violations of the code of conduct. We will
+  take action when members of our community violate this code such as
+  contacting [email protected] with the subject line SOAP Code
+  of Conduct (all emails sent in this fashion will be treated with the
+  strictest confidence) or talking privately with the person.
++ This code of conduct applies to all community situations online and
+  offline, including mailing lists, forums, social media, conferences,
+  meetings, associated social events, and one-to-one interactions.
+
+Any related activity or project organized by members of the SOAP
+community, including affiliated packages, are welcome to have their own codes
+of conduct, but agree to also abide by the present code of conduct.
+
+Parts of this code of conduct have been adapted from the PSF code of conduct and
+the Astropy code of conduct: https://www.astropy.org/code_of_conduct.html.