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

add contributing helper doc #86

Merged
merged 4 commits into from
Nov 1, 2024
Merged

add contributing helper doc #86

merged 4 commits into from
Nov 1, 2024

Conversation

xiangchenjhu
Copy link
Collaborator

No description provided.

@jamienoss
Copy link
Member

@xiangchenjhu This looks great! Would you mind adding this to https://github.com/ssec-jhu/base-template when you have some spare time, please, cheers!

BTW I opened ssec-jhu/base-template#151 for this.

@xiangchenjhu xiangchenjhu requested review from amitschang and removed request for amitschang October 31, 2024 19:59
Copy link
Member

@amitschang amitschang left a comment

Choose a reason for hiding this comment

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

looks great, thanks! One comment inline, and I also think it would probably be good to add a link to this document in the README

@amitschang
Copy link
Member

oh sorry, I missed that this is draft!

@xiangchenjhu xiangchenjhu marked this pull request as ready for review November 1, 2024 15:35
@xiangchenjhu xiangchenjhu requested a review from a team as a code owner November 1, 2024 15:36
@xiangchenjhu
Copy link
Collaborator Author

oh sorry, I missed that this is draft!

It's should have been turned to formal PR. Thanks for reminding

@xiangchenjhu
Copy link
Collaborator Author

xiangchenjhu commented Nov 1, 2024

looks great, thanks! One comment inline, and I also think it would probably be good to add a link to this document in the README

I added the link for CONTRIBUTING in README. I didn't find the comment inline you mentioned (because that's the draft PR?) Could you add it again, Thanks!

Copy link
Member

@amitschang amitschang left a comment

Choose a reason for hiding this comment

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

can you see it now?

CONTRIBUTING.md Outdated

## Making Changes

- **Coding Standards**: Follow PEP 8 for Python code. Use `ruff format` or `tox -e format` to ensure code formatting aligns with the repository’s requirements.
Copy link
Member

Choose a reason for hiding this comment

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

Here I think it would be better to just use the tox command. Fewer options is better and tox codifies more than just the formatting - we can change in it's code without changing advice here.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

That makes sense. Using tox -e format as the single command has clear advantages. I initially used ruff format . because it was mentioned in the CI error, but after running tox -e format, it made additional adjustments on 9 more files :).

Copy link
Member

@amitschang amitschang left a comment

Choose a reason for hiding this comment

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

Thanks!

@xiangchenjhu
Copy link
Collaborator Author

Thanks for the advice

@xiangchenjhu xiangchenjhu merged commit b85cc3d into main Nov 1, 2024
6 checks passed
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