Skip to content

docs: Update README.md#82

Open
acblackford wants to merge 2 commits intomainfrom
acblackford-patch-1
Open

docs: Update README.md#82
acblackford wants to merge 2 commits intomainfrom
acblackford-patch-1

Conversation

@acblackford
Copy link
Copy Markdown

Updated prose for 'Issues' section - contributions.

Updated prose for 'Issues' section - contributions.
README.md Outdated
## Issues

Please open [Github issues](https://github.com/NASA-IMPACT/csda-client/issues) with any bug reports, feature requests, and questions. You may also reach out to the CSDA Operations team at csda-support@nasa.gov.
Please open [Github issues](https://github.com/NASA-IMPACT/csda-client/issues) with any bug reports, feature requests, and questions. At this time, only contributions from CSDA team members will be accepted and merged. You may also reach out to the CSDA Operations team at csda-support@nasa.gov.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This doesn't really make sense in the context of Github issues. This would only apply to PRs.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@L-Hudgins I'd recommend this, instead:

Suggested change
Please open [Github issues](https://github.com/NASA-IMPACT/csda-client/issues) with any bug reports, feature requests, and questions. At this time, only contributions from CSDA team members will be accepted and merged. You may also reach out to the CSDA Operations team at csda-support@nasa.gov.
Please open [Github issues](https://github.com/NASA-IMPACT/csda-client/issues) with any bug reports, feature requests, and questions. You may also reach out to the CSDA Operations team at csda-support@nasa.gov.
At this time, only pull requests from CSDA team members will be accepted and merged.

L-Hudgins
L-Hudgins previously approved these changes Feb 26, 2026
Copy link
Copy Markdown

@L-Hudgins L-Hudgins left a comment

Choose a reason for hiding this comment

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

I don't see any problems with that clarification.

@L-Hudgins
Copy link
Copy Markdown

PR titles need to start with one of the following
Available types:

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit

Probably 'docs: Update README.md'

@L-Hudgins L-Hudgins changed the title Update README.md docs: Update README.md Mar 6, 2026
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