added code to read configurations from a file called .secrets\config.json instead of having to edit the script

.github/workflows/publish-script.yml

@@ -0,0 +1,41 @@
+name: Publish PowerShell Script
+
+on:
+  workflow_dispatch:
+
+jobs:
+  test-and-publish:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v3
+
+      - name: Prepare script for publishing
+        shell: pwsh
+        run: |
+          $version = Get-Content version_v3.txt
+          $content = Get-Content IntuneAssignmentChecker_v3.ps1
+          $scriptContent = @"
+          #Requires -Version 7.0
+          #Requires -Modules Microsoft.Graph.Authentication
+
+          <#PSScriptInfo
+          .VERSION $version
+          .GUID c6e25ec6-5787-45ef-95af-8abeb8a17daf
+          .AUTHOR ugurk
+          .PROJECTURI https://github.com/ugurkocde/IntuneAssignmentChecker
+          #>
+
+          <#
+          .DESCRIPTION
+          This script enables IT administrators to efficiently analyze and audit Intune assignments. It checks assignments for specific users, groups, or devices, displays all policies and their assignments, identifies unassigned policies, detects empty groups in assignments, and searches for specific settings across policies.
+          #>
+
+          "@
+          $scriptContent + ($content -join "`n`n") | Set-Content IntuneAssignmentChecker.ps1
+
+      - name: Publish to PowerShell Gallery
+        shell: pwsh
+        run: |
+          $env:PSGalleryApiKey = "${{ secrets.NUGET_KEY }}"
+          Publish-Script -Path ./IntuneAssignmentChecker.ps1 -Repository PSGallery -NuGetApiKey $env:PSGalleryApiKey -Verbose

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+https://www.linkedin.com/in/ugurkocde/.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -0,0 +1,75 @@
+# Contributing Guidelines
+
+Thank you for your interest in contributing! This document provides guidelines and steps for contributing to this project.
+
+## Code of Conduct
+
+By participating in this project, you agree to maintain a respectful and inclusive environment for everyone. Please:
+
+- Use welcoming and inclusive language
+- Be respectful of differing viewpoints and experiences
+- Accept constructive criticism gracefully
+- Focus on what is best for the community
+
+## How to Contribute
+
+### Reporting Issues
+
+- Before creating an issue, please check if a similar issue already exists
+- Provide a clear and descriptive title
+- Include detailed steps to reproduce the issue
+- Specify your environment/version information
+- Include any relevant code snippets or error messages
+
+### Pull Requests
+
+1. Fork the repository
+2. Create a new branch for your feature (`git checkout -b feature/amazing-feature`)
+3. Make your changes
+4. Commit your changes (`git commit -m 'Add some amazing feature'`)
+5. Push to the branch (`git push origin feature/amazing-feature`)
+6. Open a Pull Request
+
+### Pull Request Guidelines
+
+- Keep your changes focused and atomic
+- Update documentation as needed
+- Add tests if applicable
+- Follow the existing code style
+- Verify all tests pass
+- Include a clear description of the changes
+- Link any related issues using keywords (`Fixes #123`, `Closes #456`)
+
+## Style Guidelines
+
+- Follow the existing code style and conventions
+- Use clear, descriptive variable and function names
+- Add comments for complex logic
+- Keep functions focused and modular
+- Remove any debugging code or console logs
+- Ensure proper error handling
+
+## Development Setup
+
+1. Fork and clone the repository
+2. Install any required dependencies
+3. Follow the README.md setup instructions
+4. Make your changes in a new git branch
+
+## Documentation
+
+- Update README.md if you change functionality
+- Comment your code where necessary
+- Update any relevant documentation
+
+## Questions or Need Help?
+
+Feel free to reach out to me on [LinkedIn](https://www.linkedin.com/in/ugurkocde/) if you have any questions or need clarification.
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the same license as the original project.
+
+---
+
+Thank you for contributing to make this project better!