Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`#/components/schemas/git-user/properties/date` could have a `format: date-time`

Open
#5,476 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
openapi
Domain
api, documentation

Research direction

The issue names OpenAPI schema paths but no repository file or test. Start by searching the description source for the listed JSON pointers and inspect how schema formats are represented; done means the date, created_at, updated_at, and related key fields consistently declare format: date-time where appropriate.

Written by the indexing model from the issue text.

Description

content documentation

#/components/schemas/git-user/properties/date currently looks like this in FPT. Also in other versions.

          "date": {
            "type": "string",
            "examples": [
              "\"2007-10-29T02:42:39.000-07:00\""
            ]
          }

It would be beneficial to have format: date-time.

Other examples

#/paths/~1orgs~1{org}~1artifacts~1{subject_digest}~1metadata~1storage-records/get/responses/200/content/application~1json/schema/properties/storage_records/items/properties/created_at
#/paths/~1orgs~1{org}~1artifacts~1{subject_digest}~1metadata~1storage-records/get/responses/200/content/application~1json/schema/properties/storage_records/items/properties/updated_at
#/components/schemas/gpg-key/properties/subkeys/items/properties/created_at
#/components/schemas/gpg-key/properties/subkeys/items/properties/expires_at
Dominant language
No language data
Stars
1.6k
Forks
342
Avg merge
2h 23m
Merged PRs (30d)
57

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/rest-api-description

All issues in github/rest-api-description

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.