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 CODE_OF_CONDUCT.md #53

Merged
merged 1 commit into from
Jun 14, 2024
Merged

Update CODE_OF_CONDUCT.md #53

merged 1 commit into from
Jun 14, 2024

Conversation

GUNJESH843
Copy link
Contributor

Title

Update CODE_OF_CONDUCT.md to include Table of Contents

Description

Added a Table of Contents to the Contributor Covenant Code of Conduct in the README.md to improve navigation and user experience. No additional dependencies are required for this change.


Issue Ticket Number

Fixes #50


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

Checklist:

  • I have followed the contributing guidelines of this project as mentioned in CONTRIBUTING
  • I have checked to ensure there aren't other open Pull Requests for the same update/change?
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes needed to the documentation

@jatiinyadav jatiinyadav merged commit 1ed0fd3 into jatiinyadav:master Jun 14, 2024
1 check passed
@GUNJESH843
Copy link
Contributor Author

@jatiinyadav hey you forgot the GSSOC contributor labe for this pr please look into it.

@jatiinyadav jatiinyadav added the gssoc An issue for GSSOC'24 label Jun 15, 2024
@GUNJESH843
Copy link
Contributor Author

hey, @jatiinyadav will I not be getting a level badge for these PRs,
sorry to ask you again and again.

@GUNJESH843
Copy link
Contributor Author

Hi @jatiinyadav,

I wanted to follow up on my previous message regarding the level badge for my PRs.
Could you please label them as level 1 so that I can receive points for them? Your assistance would be greatly appreciated.

Thank you for considering my request.

@jatiinyadav
Copy link
Owner

Hi @jatiinyadav,

I wanted to follow up on my previous message regarding the level badge for my PRs. Could you please label them as level 1 so that I can receive points for them? Your assistance would be greatly appreciated.

Thank you for considering my request.

Screenshot 2024-06-16 123228
Hi @GUNJESH843,

  1. As I already mentioned here, updating only README.md will not considered Level 1, you have to update other files as well to get Level 1.
  2. You will not be given level 1 on each Pull Request., it will considered as spam.
  3. It cannot be marked as level 2 because it is just a Documentation change, and to be more precise it's you only the Table of Contents, You can check Level 2 tickets here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gssoc An issue for GSSOC'24
Projects
None yet
Development

Successfully merging this pull request may close these issues.

📝[Docs]: Add Table of Contents to README file.
2 participants