Adjust table column widths with 10:1 ratio and fix issue URL links

[Copilot]

Pull Request

Description

Markdown tables in build reports now use column width hints for better PDF rendering. Issue IDs (typically short) render in a narrow, centered column while titles (typically verbose) get 10x more space. Additionally, fixed a bug where issue links pointed to API endpoints instead of web pages.

Changes:

• Modified table separators from |-------|-------| to | :-: | :---------- |
• Updated AppendChangesSection(), AppendBugsFixedSection(), and AppendKnownIssuesSection()
• Fixed CreateItemInfoFromIssue() to use issue.HtmlUrl instead of issue.Url
• Added test coverage for table formatting validation

Result:

| Issue | Title |
| :-: | :---------- |
| [123](https://github.com/owner/repo/issues/123) | Add new feature for data processing |

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Code quality improvement

Related Issues

Issue linking handled automatically by the system.

Pre-Submission Checklist

Before submitting this pull request, ensure you have completed the following:

Build and Test

• Code builds successfully: dotnet build --configuration Release
• All tests pass: dotnet test --configuration Release
• Code produces zero warnings

Code Quality

• Code formatting is correct: dotnet format --verify-no-changes
• New code has appropriate XML documentation comments
• Static analyzer warnings have been addressed

Quality Checks

Please run the following checks before submitting:

• Spell checker passes: cspell "**/*.{md,cs}"
• Markdown linter passes: markdownlint "**/*.md"
• YAML linter passes: yamllint '**/*.{yml,yaml}'

Testing

• Added unit tests for new functionality
• Updated existing tests if behavior changed
• All tests follow the AAA (Arrange, Act, Assert) pattern
• Test coverage is maintained or improved

Documentation

• Updated README.md (if applicable)
• Updated ARCHITECTURE.md (if applicable)
• Added code examples for new features (if applicable)
• Updated requirements.yaml (if applicable)

Additional Notes

The markdown column width syntax (:-: for center, :---------- for wide left-align) is interpreted by most markdown renderers including PDF generators. The 10:1 dash ratio provides appropriate visual weighting for short IDs vs long titles.

The bug fix ensures that issue links in generated markdown tables now correctly point to GitHub web pages (e.g., https://github.com/owner/repo/issues/123) instead of API endpoints (e.g., https://api.github.com/repos/owner/repo/issues/123), providing a better user experience. This makes CreateItemInfoFromIssue() consistent with CreateItemInfoFromPullRequest() which was already using HtmlUrl.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Feature]: Table Width</issue_title>
<issue_description>### Problem Statement

The table widths should be adjusted so the Issue ID column is narrow.

Proposed Solution

Modify the markdown table to use dash-counts for column widths, and colons for centering. For example:

| Issue | Title |
| :-: | :---------- |
| 1 | Some long title |

10:1 should be acceptable because IDs tend to be short (a few digits) and the titles tend to be quite verbose.

Alternatives Considered

No response

Usage Examples

Benefits

Table rendering in PDFs is much easier to read.

Priority

Medium - Would improve my workflow

Willingness to Contribute

Yes, I can submit a pull request

Additional Context

No response

Checklist

• I have searched existing issues to ensure this is not a duplicate
• I have provided a clear description of the feature
• I have explained why this feature would be useful</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [Feature]: Table Width #42

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Malcolmnixon]

@copilot I just noticed the Issue URL links in the table don't go to web pages but instead provide json rest data. I believe CreateItemInfoFromIssue needs to use the HtmlUrl of the issue.

[Copilot]

@copilot I just noticed the Issue URL links in the table don't go to web pages but instead provide json rest data. I believe CreateItemInfoFromIssue needs to use the HtmlUrl of the issue.

Fixed in commit f40f1a7. Changed CreateItemInfoFromIssue to use issue.HtmlUrl instead of issue.Url so issue links now point to the web page rather than the API endpoint.