wordpress-mobile / wordpress-mobile/release-toolkit
Add action to download the source code `tar.gz` of a GitHub release
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 31
- Forks
- 10
- Avg merge
- 5h 45m
- Merged PRs (30d)
- 2
Description
Since moving to XCFramework as the integration method for Gutenberg for Mobile Apps, we have been downloading the source code via Git in order to generate strings, see https://github.com/wordpress-mobile/WordPress-iOS/pull/21416.
Needless to say, checking out the whole repo take a long time, even with --depth 1, which is one of the reasons we moved to XCFramework in the first place.
As we work to hand over release management to the devs, see https://github.com/Automattic/apps-infra-plans/issues/5, it would be good to take the time to remove this bottleneck.
One idea I have is to download the source code from the GitHub release (assuming a release is used, which is in most of the integration cases). After all, what we don't need Git history, only a snapshot of the code.
For reference, the archive for version 1.109.2 is around 20 MB
Contributor guide
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
No file, test, or entry point is named. Start by tracing the release automation that currently checks out Git source, then identify the action responsible for obtaining release contents. Done means the action can use a GitHub release tar.gz snapshot instead of a full repository checkout, while preserving the source needed for string generation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, ruby
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100