📖 [Docs]: Scope issue and PR references by repository (local, remote, external)

[Marius Storhaug (MariusStorhaug)]

The Ways of Working now explain where issue and pull request references belong, and how to format them. References live in issues and pull requests — not in commit messages — and are scoped to where they resolve.

Changed: How issues, PRs, and commits reference each other

• Same repository — use the #123 shorthand.
• Another repository — use the fully qualified Owner/Repo#123 form so the link resolves to the right repository.
• Outside GitHub (Jira, Confluence, Slack, external docs, release announcements) — use the full URL, since no GitHub autolinking applies.
• Commit messages — carry no issue or PR references at all. The pull request links the work to its issue (via a closing keyword such as Fixes #123); commits describe the change itself.

Updated documents:

• Issue Format gains a "Properties of every issue" rule covering the same-repo, cross-repo, and external cases.
• PR Format scopes the Related issues rule the same way, and its examples now model both forms — a same-repo Fixes #123 alongside a cross-repo PSModule/Process-PSModule#124.
• Commit Conventions rule 5 now keeps issue and PR references out of commit history entirely.

Technical Details

• src/docs/Ways-of-Working/Issue-Format.md: new bullet under "Properties of every issue".
• src/docs/Ways-of-Working/PR-Format.md: §4 Related issues rule reworded; same-repo examples use #123/#218/#219, the cross-repo example keeps Owner/Repo#N.
• src/docs/Ways-of-Working/Commit-Conventions.md: rule 5 changed from "reference issues" to "keep issue and PR references out of commit messages".
• Implementation plan progress: all three tasks in Scope issue and PR references to the target repository #49 completed.

Related issues

• Fixes Scope issue and PR references to the target repository #49

[Marius Storhaug (MariusStorhaug)]

CI note — the failing Lint check is pre-existing and unrelated to this change.

super-linter validates the entire codebase, and main is already red: commit 99d9d5a introduced MD060/table-column-style violations in continuous-x-and-continuous-ai.md, devops-reference.md, and development-practices.md (the markdownlint config at .github/linters/.markdown-lint.yml does not disable MD060).

None of the three files changed here — Issue-Format.md, PR-Format.md, Commit-Conventions.md — are flagged. Build, CodeQL, and both Analyze checks pass.

Making main green again (either reformatting the offending tables or adding MD060: false to .github/linters/.markdown-lint.yml) is a separate change and intentionally out of scope here.

[Marius Storhaug (MariusStorhaug)]

Tracked separately in #51.