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

Enhance the contributing guide in online doc #123

Merged
merged 2 commits into from
Nov 29, 2021

Conversation

nhuet
Copy link
Contributor

@nhuet nhuet commented Nov 25, 2021

Add sections and reorganize into:

  • setting up dev environment
    • installation from source in dev mode
    • local build of the docs
    • running tests
  • guide lines when coding
    • code linters
    • notebooks convention
    • adding tests
  • pull request process

You can preview the resulting page here (github markdown interpreting). Or have a complete view of resulting documentation by downloading the "doc" artifact from the "Build scikit-decide" action triggered by this PR , and then:

mkdir testdoc
cd testdoc
unzip path/to/doc.zip -d scikit-decide
python -m http.server

Add sections and reorganize into

- setting up dev environment
  - installation from source in dev mode
  - local build of the docs
  - running tests
- guide lines when coding
  - code linters
  - notebooks convention
  - adding tests
- pull request process
@nhuet nhuet force-pushed the nh/doc_complete_contribute_page branch from f3357c8 to 7f6d61c Compare November 25, 2021 20:52
@nhuet nhuet changed the title Add a contributing guide to online doc Enhance the contributing guide in online doc Nov 25, 2021
@nhuet nhuet closed this Nov 26, 2021
@nhuet nhuet deleted the nh/doc_complete_contribute_page branch November 26, 2021 08:56
@nhuet nhuet restored the nh/doc_complete_contribute_page branch November 26, 2021 08:56
@nhuet nhuet reopened this Nov 26, 2021
- [check the documentation locally](#building-the-docs-locally) if you modified it
- check you respect the coding styles by [running linters](#coding-style-and-code-linting)

I you do not, you will still be able to see the status of your PR as CI will do that checks for you.
Copy link
Contributor

Choose a reason for hiding this comment

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

2 typos: If ... these checks for you

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done


- Fork the repository on github.
- Clone your fork on your computer.
- Create a branch with a self-explanatory branch, e.g. `xx/add-solver-crazyalgoname` where "xx" stands for your initials,
Copy link
Contributor

Choose a reason for hiding this comment

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

External contributors do not need to follow this naming scheme, they can use their master branch if they want.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

- having a separate commit to reformat previous existing code if necessary
- rewritting commit messages so that it explains the changes made and why, the "how" part being explained by the code itself
(see this [post](https://chris.beams.io/posts/git-commit/) about what a commit message should and should not contain)
- rebasing on main repository main branch if it diverged too much by the time you finished
Copy link
Contributor

Choose a reason for hiding this comment

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

upstream repository's master branch

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

@dbarbier dbarbier mentioned this pull request Nov 26, 2021
10 tasks
@galleon galleon merged commit cbd9a9f into airbus:master Nov 29, 2021
@nhuet nhuet deleted the nh/doc_complete_contribute_page branch December 13, 2021 11:09
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.

3 participants