Add ctx propagation to raw api request

[kerobbi]

Update newRequest to accept a context.Context param and attach it to the generated http.Request using withContext.

This change ensures that trace contexts are correctly propagated, supporting distributed tracing in the remote MCP server.

[Copilot]

Pull Request Overview

This PR adds context propagation to the low-level newRequest helper, ensuring that trace and cancellation contexts flow through HTTP calls in the raw API client.

• Extended newRequest to accept a context.Context and attach it via WithContext
• Updated GetRawContent to pass the incoming ctx into newRequest
• Adjusted error handling in newRequest to return early on failure before setting context

Comments suppressed due to low confidence (3)

pkg/raw/raw.go:65

• Add or update unit tests to verify that the provided context is actually attached to the outgoing http.Request and that cancellations/timeouts are honored.

func (c *Client) GetRawContent(ctx context.Context, owner, repo, path string, opts *RawContentOpts) (*http.Response, error) {

pkg/raw/raw.go:28

• Make sure to import the "context" package at the top of this file, otherwise context.Context will be undefined.

func (c *Client) newRequest(ctx context.Context, method string, urlStr string, body interface{}, opts ...gogithub.RequestOption) (*http.Request, error) {

pkg/raw/raw.go:67

• Review other methods in this file (or in downstream code) that call newRequest to ensure they’ve been updated to pass ctx as the first argument, preventing build failures and ensuring consistent context propagation.

	req, err := c.newRequest(ctx, "GET", url, nil)

[SamMorrowDrums]

Just to validate, does this work if you try it locally? I assume so, but an alternative is to take the current request context and then extend it and add it back to the request.

[kerobbi]

Just to validate, does this work if you try it locally? I assume so, but an alternative is to take the current request context and then extend it and add it back to the request.

I did test this locally and confirmed that ctx propagation is working as expected, trace info and parent-child spans are all showing up correctly.

I'm a bit confused about the suggested alternative. Since we are creating a new outbound request here (not working with an incoming HTTP request), I don't think there's an existing req ctx to extend? Let me know if I'm missing something.