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

[UPDATE] added contributing guidelines #3167

Merged
merged 2 commits into from Oct 4, 2022

Conversation

nikhilbhatt
Copy link
Contributor

Resolves #3158

Description

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • Documentation update

How Has This Been Tested?

Screenshots

@nikhilbhatt nikhilbhatt force-pushed the change_readme branch 4 times, most recently from 85d546a to e584594 Compare October 2, 2022 18:28

1. Add a test for your change. If you are adding functionality or fixing a bug, you should add a test!

1. Run linters and fix any linting errors they brings up.
Copy link
Member

Choose a reason for hiding this comment

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

I don't think this repo uses these git hooks.

Copy link
Member

Choose a reason for hiding this comment

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

I think I'd recommend changing this to having the user run 'rubocop -a' like is recommended in the readme file :)

@seanmarcia
Copy link
Member

Thanks for this! Looks great now :)

@seanmarcia seanmarcia merged commit 6a1e8e5 into rubyforgood:main Oct 4, 2022
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.

Add Contributing File
2 participants