The type of repository.created_at property in webhook payload is int, expected type is string

[BinTianqi]

Select Topic Area

Bug

Body

Bug description

Here is the request headers

Request method: POST
Accept: */*
Content-Type: application/json
User-Agent: GitHub-Hookshot/0f7d629
X-GitHub-Delivery: 4f0a17c6-d01b-11ef-9826-2bc1ad4128c6
X-GitHub-Event: push
X-GitHub-Hook-ID: 512670721
X-GitHub-Hook-Installation-Target-ID: 1044308
X-GitHub-Hook-Installation-Target-Type: integration

and the request payload (some properties not relevant to this bug have been omitted)

{
  "ref": "refs/heads/master",
  "before": "0000000000000000000000000000000000000000",
  "after": "0c7ee11de6c764becff247dd77db3a3edec5a4f3",
  "repository": {
    "id": 915280444,
    "node_id": "R_kgDONo4SPA",
    "created_at": 1736599727,
    "updated_at": "2025-01-11T12:48:47Z",
    "pushed_at": 1736600117
  },
  "sender": {
    "login": "BinTianqi",
    "id": 146811279,
    "node_id": "U_kgDOCMApjw"
  },
  "installation": {
    "id": 56926564,
    "node_id": "MDIzOkludGVncmF0aW9uSW5zdGFsbGF0aW9uNTY5MjY1NjQ="
  }
}

In the REST API docs, the created_at property of a repository is string or null, not int.

Reproduce this bug

1. Register a github app and configure its webhook, subscribe to push event
2. Install this app to your account, grant All repositories access
3. Create a repository
4. Add this remote repo in a local git repo
5. git push
6. Go to advanced settings of this app, view recent deliveries. Find the delivery triggered by push event
7. In the delivery's payload, the repository.created_at and repository.pushed_at property's type is int

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[ca1ik]

It seems there is a discrepancy between the data type of the repository.created_at and repository.pushed_at properties in the webhook payload and the expected data type specified in the REST API documentation.

We understand how this inconsistency could cause confusion or issues when processing webhook payloads. This feedback is valuable, and we will investigate further to ensure the webhook payload aligns with the documented API behavior.

Your detailed reproduction steps and context are greatly appreciated and will help us address the problem more effectively. Thank you for bringing this to our attention!