Adjust "Release artifacts" wording in GitHub Releases
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
-
I don't think mentioning "Custom ROM" is necessary. "Aftermarket custom operating system" should "ring a bell" to the user if they have installed a custom operating system themselves and maybe also in some other special situations. This is a small thing but removing it also makes the release notes slightly shorter.
-
I think "the" should be added to "Users on Huawei devices running original operating system" ("Users on Huawei devices running the original operating system"). It could also be added for "These versions are also distributed through Huawei AppGallery" ("These versions are also distributed through the Huawei AppGallery.")
-
"Do not use it if you want to install microG regularly." Install microG regularly?
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 locating the "Release artifacts" wording in the GitHub Releases source or template. Review the requested removals and grammar changes, then clarify the intended replacement for "install microG regularly" before editing. Done means the release wording reflects the agreed changes and remains concise.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, github
- Domain
- documentation, mobile, release
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100