luanti-org / luanti-org/contentdb
[FEATURE] Use the user's timezone in the dates
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 115
- Forks
- 62
- Avg merge
- 19h 7m
- Merged PRs (30d)
- 5
Description
Problem
When making automatic releases, it automatically sets the date as the release's name for you (for example 2020-03-5).
But when it's night here, it increases one day, instead of the current day I am on (say 2021-07-03, instead of 2021-07-02).
When looking at the releases, it automatically writes the date below the release's name. The date sometimes's wrong, too, because the timezone is set differently from mine.
Solutions
It'd be great to use the user's timezone for the dates to be accurate.
Alternatives
I don't have any alternatives in mind. If you have any, please write them below.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points; start by tracing where automatic release names and the dates shown below releases are generated. Check how the current timezone is obtained and run any existing release or date-related tests. Done means both dates reflect the user's timezone consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100