Add documentation for declaring module dependencies via #Requires#292
Draft
Add documentation for declaring module dependencies via #Requires#292
Conversation
Copilot started work on behalf of
Marius Storhaug (MariusStorhaug)
March 12, 2026 09:48
View session
Copilot
AI
changed the title
[WIP] Add usage documentation for processes
Add documentation for declaring module dependencies via #Requires
Mar 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Users adding
RequiredModulestosrc/manifest.psd1get silent data loss — the entries are not propagated to the built manifest. The correct approach (#Requires -Modulesin individual function files) was undocumented.Changes
manifest.psd1andfunctions/entries to clarify thatRequiredModulesis not read from the source manifest, and that#Requires -Modulesstatements in function files are compiled into the built manifest#Requires -Modulesat the top of individual function filesModuleVersion,RequiredVersion)RequiredModulesin the final manifestExample — correct way to declare a module dependency:
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
https://api.github.com//usr/bin/curl curl -s -o /dev/null -w %{http_code} --max-time 5 REDACTED(http block)https://api.github.com/graphql/usr/bin/gh gh label list --repo PSModule/Process-PSModule(http block)/usr/bin/gh gh api graphql -f query={ repository(owner:"PSModule",name:"Process-PSModule") { labels(first:50) { nodes { name } } } }(http block)/usr/bin/gh gh issue create --repo PSModule/Process-PSModule --title Add documentation for defining module dependencies using #Requires statements --body-file /tmp/issue-body.md --label NoRelease(http block)https://api.github.com/repos/PSModule/Process-PSModule/issues/usr/bin/curl curl -s -o /tmp/issue-response.json -w %{http_code} -X POST -H Authorization: token ****** -H Accept: application/vnd.github+json -H X-GitHub-Api-Version: 2022-11-28 REDACTED -d {"title": "Add documentation for defining module dependencies using #Requires statements", "body": "## Context\n\nWhen building a PowerShell module withProcess-PSModule, developers often need to declare that their module depends on other modules (e.g.,(http block)/usr/bin/curl curl -s -X POST -H Authorization: token ****** -H Accept: application/vnd.github+json -H X-GitHub-Api-Version: 2022-11-28 REDACTED -d {"title": "Add documentation for defining module dependencies using #Requires statements", "body": "## Context\n\nWhen building a PowerShell module withProcess-PSModule, developers often need to declare that their module depends on other modules (e.g.,(http block)/home/REDACTED/work/_temp/copilot-developer-action-main/github-mcp-server/github-mcp-server /home/REDACTED/work/_temp/copilot-developer-action-main/github-mcp-server/github-mcp-server stdio(http block)https://api.github.com/repos/PSModule/Process-PSModule/issues/293/labels/home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node -e const https = require('https'); const data = JSON.stringify({labels: ['NoRelease']}); const options = { hostname: 'api.github.com', port: 443, path: '/repos/PSModule/Process-PSModule/issues/293/labels', method: 'POST', headers: { 'Authoriza git nfig�� HEAD(http block)https://api.github.com/repos/PSModule/Process-PSModule/labels/usr/bin/gh gh api repos/PSModule/Process-PSModule/labels --jq .[].name(http block)https://api.github.com/user/usr/bin/curl curl -v -s -o /dev/null -w \nHTTP_CODE: %{http_code} -H Authorization: token ****** -H Accept: application/vnd.github+json REDACTED(http block)/usr/bin/curl curl -s -w \nHTTP_CODE: %{http_code} -H Authorization: ****** -H Accept: application/vnd.github+json -H X-GitHub-Api-Version: 2022-11-28 REDACTED(http block)If you need me to access, download, or install something from one of these locations, you can either:
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.