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

Adds documents for guidelines on contributing #149

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

thomas-robinson
Copy link
Member

This PR adds the instructions for contributing to coupler including a contribution guide, a code style guide, and a code of conduct with expected behavior. There is also a link to the contribution guide at the top of the README so people will see it immediately when they visit the main page of this repo.

Updates README with link to Contirubting guide
@thomas-robinson
Copy link
Member Author

Resolved #150

CODE_STYLE.md Outdated Show resolved Hide resolved
CODE_STYLE.md Outdated Show resolved Hide resolved
CODE_STYLE.md Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
@@ -82,6 +83,12 @@ GFDL schedule that addresses the needs of the GFDL scientists. We follow the
workflow, briefly described in the [Quick Start Workflow](#quick-start-workflow)
section.

Any changes that are required for a PR in the FMScoupler should be linked. Merges
should take place downstream first in order to ensure new dependencies are
available. Changes made to componenet models that change calls in the
Copy link
Contributor

Choose a reason for hiding this comment

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

Typo "componenet"

- Complexity
- Are the changes easily understood by the reader / reviewer?
- Testing
- Code changes should include a test program or a modification to a test program to ensure the code is covered by the test suite
Copy link
Contributor

Choose a reason for hiding this comment

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

We don't have a test suite for the coupler so should we take this out?

unit tests, code coverage tests, and regression tests for new and existing code
in yaml (.yml) files. Github provides a guide
(https://help.github.com/en/articles/about-continuous-integration) for
implementing CI tests.
Copy link
Contributor

Choose a reason for hiding this comment

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

Might be good to mention the null_model script in this section, since thats the only real test we use in this repository besides our alpha/beta testing.

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