feat(background-file) Add the background-file CLI option

[Victor-D]

feat(background-file) Add the background-file CLI option to read a local business context file

Description

Following discussion in #176 add the new -B flag :

  -b, --background string       optional requirement/business context for the review
  -B, --background-file string  path to a Markdown file used as review background (combined with --background; inline value appears first when both are set)

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Refactoring (no functional changes)
• Documentation update
• CI / Build / Tooling

How Has This Been Tested?

• make test passes locally
• Manual testing (describe below)

soft limit

% ./dist/opencodereview review --repo /home/USER/bitbucket/REPO_NAME --commit <commit-hash> -B /tmp/context.md
[ocr] --background-file content is 4623 characters, exceeding the recommended 2000 (continuing but review quality might be impacted)
[ocr] 2 file(s) changed, reviewing 1 in /home/USER/bitbucket/REPO_NAME
[ocr] Skipping hieradata/roles/web.eyaml — filtered by path/extension rules
[ocr] Filtered 1 file(s) by include/exclude rules

hard limit

user@HOSTNAME open-code-review % ./dist/opencodereview review --repo /home/USER/bitbucket/REPO_NAME --commit <commit-hash> -B /tmp/context.md
Error: background content is 14631 characters, exceeding the hard limit of 8000 (aborting)

I also checked I see the two prompts in the session file when using -b and -B flags.

Checklist

• My code follows the project's coding style (go fmt, go vet)
• I have performed a self-review of my code
• I have added tests that prove my fix is effective or my feature works
• New and existing unit tests pass locally with my changes
• I have updated the documentation accordingly (if applicable)
• I have signed the CLA

Related Issues

[CLAassistant]

All committers have signed the CLA.

[github-actions]

🔍 OpenCodeReview found 2 issue(s) in this PR.

• ✅ 2 posted as inline comment(s)
• 📝 0 posted as summary