Skip to content

Conversation

chaitaliKundu
Copy link
Contributor

PR Description:

replace this with your description

Pull Request Checklist

Overview

  • Put an x inside of the square brackets to check each item.
  • I have read and understood the CONTRIBUTING.md guidelines
  • My pull request has a descriptive title that accurately reflects the changes and the description has been filled in above.
  • I've included only files relevant to the changes described in the PR title and description
  • I've created a new branch in my forked repository for this contribution

Code Quality

  • My code is relevant to ServiceNow developers
  • My code snippets expand meaningfully on official ServiceNow documentation (if applicable)
  • I've disclosed use of ES2021 features (if applicable)
  • I've tested my code snippets in a ServiceNow environment (where possible)

Repository Structure Compliance

  • I've placed my code snippet(s) in one of the required top-level categories:
    • Core ServiceNow APIs/
    • Server-Side Components/
    • Client-Side Components/
    • Modern Development/
    • Integration/
    • Specialized Areas/
  • I've used appropriate sub-categories within the top-level categories
  • Each code snippet has its own folder with a descriptive name

Documentation

  • I've included a README.md file for each code snippet
  • The README.md includes:
    • Description of the code snippet functionality
    • Usage instructions or examples
    • Any prerequisites or dependencies
    • (Optional) Screenshots or diagrams if helpful

Restrictions

  • My PR does not include XML exports of ServiceNow records
  • My PR does not contain sensitive information (passwords, API keys, tokens)
  • My PR does not include changes that fall outside the described scope

@rohi-v rohi-v self-assigned this Oct 13, 2025
@rohi-v
Copy link
Contributor

rohi-v commented Oct 13, 2025

Hi @chaitaliKundu

Thankyou for your contribution.

For Hacktoberfest, we’re aiming for high-quality contributions providing real-world developer usecases. Low-effort pull requests will be marked accordingly.

we appreciate the effort you’ve put into this contribution. Since this is your first PR, we’ve labeled it as hacktoberfest-accepted so it still counts toward your Hacktoberfest progress.

@rohi-v rohi-v added the hacktoberfest-accepted The PR is accepted for Hacktoberfest, regardless of being merged or not label Oct 13, 2025
@rohi-v rohi-v closed this Oct 13, 2025
@chaitaliKundu
Copy link
Contributor Author

@rohi-v - Thanks for your comment. is this type of contribution not accepted ? or take time for accept the PR ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hacktoberfest-accepted The PR is accepted for Hacktoberfest, regardless of being merged or not

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants