OpenRCT2 / OpenRCT2/Localisation
[Idea] Translation status on README.md
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 72
- Forks
- 213
- Avg merge
- 10h 33m
- Merged PRs (30d)
- 20
Description
I've stumbled recently on a nice GitHub action which does changes to README.md. In this case it looks for a RSS feed of a blog and changes README.md with the recent posts.
The workflow: https://github.com/marketplace/actions/blog-post-workflow
The workflow in action: https://www.youtube.com/watch?v=ECuqb5Tv9qI&t=427s
I've came up with an idea to post on README.md the current status of the translations. The action would be triggered by merging a PR / a commit to master branch and if there are any changes it would create a commit to README.md
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
Start by reviewing README.md and the repository's existing translation and workflow conventions. Define how translation status should be represented and when merged changes should update the README; the work is done when the GitHub Action updates the status reliably after the relevant merges.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, documentation, localization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100