Skip to content
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.

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

New guidelines for developpers #319

Closed
wants to merge 1 commit into from
Closed

New guidelines for developpers #319

wants to merge 1 commit into from

Conversation

Gab-D-G
Copy link
Collaborator

@Gab-D-G Gab-D-G commented Sep 27, 2023

No description provided.

@Gab-D-G Gab-D-G requested a review from gdevenyi September 27, 2023 20:54
@Gab-D-G
Copy link
Collaborator Author

Gab-D-G commented Sep 27, 2023

@gdevenyi please review contributing.md

@@ -22,7 +22,7 @@
author = 'CoBrALab'

# The full version, including alpha/beta/rc tags
release = '0.4.6'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be a seperate commit

Comment on lines +21 to +25
1. On github, fork the RABIES repository to have your own copy.
2. Clone your repository to carry out local modifications and testing. Use the `--recursive` option to download the submodules together with the main RABIES package.
3. Make your modifications to the code.
4. Testing and debugging: install your updated version of the package with ```python setup.py install```, using a proper dev environment (see above). Your can test the workflow with specific parameters by editing the ```debug_workflow.py``` script, and executing in debug mode with Spyder (see below). Before commiting changes, make sure that running ```error_check_rabies.py``` completes with no error.
5. Commit and push your modifications to Github, and create a pull request from your forked repo to the original.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to mention making a branch

@@ -5,4 +5,4 @@ sphinx-rtd-theme
sphinxcontrib-bibtex
sphinxcontrib-programoutput==0.17
jinja2==3.1.1
rabies==0.4.7
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should have a seperate commit with the version changes above

import os
import pathlib
import SimpleITK as sitk
import numpy as np
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is another separate commit

@Gab-D-G
Copy link
Collaborator Author

Gab-D-G commented Oct 4, 2023

This branch is replaced by the documentation branch #331 , where the commit history is in line with @gdevenyi's feedback. The pull request will be closed.

@Gab-D-G Gab-D-G closed this Oct 4, 2023
@Gab-D-G Gab-D-G deleted the docu_updates branch October 4, 2023 19:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants