Fix HTTP 404 in issue comment step due to missing issue_number

[Copilot]

github.rest.issues.createComment (octokit v18+) builds the request URL from issue_number, not number. Spreading context.issue only provides {owner, repo, number}, leaving issue_number undefined and producing a malformed API URL (issues//comments), causing HTTP 404.

Changes

• issue_to_bib.yml and arxiv_to_publications_correct.yml: replace ...context.issue with ...context.repo, issue_number: context.issue.number in the createComment call

// Before
github.rest.issues.createComment({...context.issue, body: process.env.COMMENT})

// After
github.rest.issues.createComment({...context.repo, issue_number: context.issue.number, body: process.env.COMMENT})

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[pancetta]

@copilot Maybe this is about the double "//" in https://api.github.com/repos/Parallel-in-Time/parallel-in-time.github.io/issues//comments ?

[Copilot]

@copilot Maybe this is about the double "//" in https://api.github.com/repos/Parallel-in-Time/parallel-in-time.github.io/issues//comments ?

Yes, exactly. ...context.issue spreads as {owner, repo, number}, but github.rest.issues.createComment builds the URL path from issue_number (not number), so issue_number was undefined → the URL became .../issues//comments.

Fixed in c6afc52 by replacing ...context.issue with ...context.repo, issue_number: context.issue.number.