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

Improve Contributor Guide #6127

Closed
wants to merge 11 commits into from
Closed

Conversation

RichardChukwu
Copy link
Contributor

@RichardChukwu RichardChukwu commented Feb 10, 2025

part of open-telemetry/sig-contributor-experience#31

Changes

  • Troubleshooting & Platform-Specific Guidance
  • Includes a troubleshooting section for common errors (e.g., CS1705 version conflicts).

Review Notes

Feedback is welcome on the troubleshooting section—are there additional issues contributors commonly face?
Let me know if any formatting improvements are needed.

Merge requirement checklist

  • CONTRIBUTING guidelines followed (license requirements, nullable enabled, static analysis, etc.)

Copy link
Contributor

This PR was marked stale due to lack of activity and will be closed in 7 days. Commenting or pushing will instruct the bot to automatically remove the label. This bot runs once per day.

@github-actions github-actions bot added the Stale Issues and pull requests which have been flagged for closing due to inactivity label Feb 25, 2025
Copy link
Contributor

@rajkumar-rangaraj rajkumar-rangaraj left a comment

Choose a reason for hiding this comment

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

Thanks for the contribution! However, we currently do not have any reported issues in the repo related to CS1705 version conflicts, and this is not a commonly encountered error in our context. Expanding the contributing guide with this information might lead to confusion rather than providing value. Given this, I don't think we should include this update. I’ll be closing this PR for now. Feel free to reopen if there’s a strong case based on actual occurrences in our repo.

@RichardChukwu
Copy link
Contributor Author

Thanks for the contribution! However, we currently do not have any reported issues in the repo related to CS1705 version conflicts, and this is not a commonly encountered error in our context. Expanding the contributing guide with this information might lead to confusion rather than providing value. Given this, I don't think we should include this update. I’ll be closing this PR for now. Feel free to reopen if there’s a strong case based on actual occurrences in our repo.

Duly noted. Thank you for the feedback

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Documentation related Stale Issues and pull requests which have been flagged for closing due to inactivity
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants