Add unit tests for internal/github issue comments and assignee management calls

[Jagadeeshftw]

📌 Description

internal/github/issues_comments.go (CreateIssueComment, DeleteIssueComment) and internal/github/assignees.go (AddIssueAssignees, RemoveIssueAssignees) drive the issue-application workflow (apply, assign, unassign, withdraw, reject) but have no tests. These are the actions a maintainer triggers from internal/handlers/issue_applications.go.

💡 Why it matters: Incorrect request shapes or unhandled error statuses here corrupt the visible state on contributors' GitHub issues; tests pin the HTTP contract.

🧩 Requirements and context

• Use httptest.Server to assert request method, path, and JSON body for each call.
• Cover success, 404 (missing issue), and 403 (permission) responses with appropriate error mapping.
• Confirm assignees are sent as the GitHub-expected {"assignees": [...]} shape.
• Confirm the comment body is sent as {"body": "..."}.
• No real GitHub network access.

Non-functional requirements

• Must be secure, tested, and documented.
• Should be efficient and easy to review.

🛠️ Suggested execution

1. Fork the repo and create a branch

git checkout -b test/github-comments-assignees

2. Implement changes

• Write/modify the relevant source: small refactor to inject base URL if needed
• Write comprehensive tests: internal/github/issues_comments_test.go, internal/github/assignees_test.go
• Add documentation: GoDoc on the request shapes
• Include GoDoc comments on error mapping
• Validate security assumptions: token header set, not logged

3. Test and commit

• Run tests:

go test ./internal/github/...

• Cover edge cases: 404, 403, empty assignee list, server 500
• Include test output and security notes in the PR description.

Example commit message

test(github): cover issue comment and assignee API calls

✅ Acceptance criteria

• Request method/path/body asserted for all four functions
• Success and error statuses mapped and tested
• Assignee/comment JSON shapes verified
• No real network calls

🔒 Security notes

Verifies the Authorization header is set and never appears in logs or test output.

📋 Guidelines

• Minimum 95% test coverage
• Clear documentation
• Timeframe: 96 hours

[xx7412421-cloud]

Hi, I would like to work on this issue if it is still available.

Planned approach:

• Add focused httptest-based unit tests for internal/github/issues_comments.go and internal/github/assignees.go.
• Assert method, path, Authorization header presence, and GitHub JSON request shapes for comment and assignee operations.
• Cover success, 404, 403, and one server-error path without any real GitHub network access.
• Keep any production-code refactor minimal and limited to testability, such as injectable base URL only if needed.

I will wait for assignment before opening a PR so this follows the GrantFox workflow.

[clintjeff2]

Hello, I have 6 years of experience working on tasks like this and handling similar challenges across backend, frontend, and smart-contract development. I have carefully read and fully understood the task requirements, and I am confident I can deliver a clean, efficient, and well-tested solution promptly. I always ensure high-quality implementation, maintainability, and adherence to best practices.

Pull request in 5 hours.