Skip to content

Conversation

@prashantmrshine
Copy link
Contributor

@prashantmrshine prashantmrshine commented Oct 26, 2025

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

@ravichandra1998g ravichandra1998g self-assigned this Oct 26, 2025
@ravichandra1998g
Copy link
Contributor

Hi @prashantmrshine

Thankyou for your submission.

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

For Hacktoberfest, we’re aiming for high-quality contributions providing real-world developer use cases.

This cannot be merged as this is a simple Business Rule
You can see some of the recently merged PRs to know the kind of code snippets we are aiming for.

Please contribute with more dynamic use cases/context.
Closing this for now. Once you make additional changes, feel free to re-open this Pull Request or create a new one.

@ravichandra1998g ravichandra1998g added the hacktoberfest-accepted The PR is accepted for Hacktoberfest, regardless of being merged or not label Oct 26, 2025
@prashantmrshine prashantmrshine deleted the HactoberFest-2025-(2nd-pull-request) branch October 26, 2025 06:00
@prashantmrshine
Copy link
Contributor Author

This is not the correct reason to reject this PR, there are many code with 2 lines accepted, we are talking about contributions there are hundreds of codes which are simple, why those are accepted.

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