wordpress-mobile / wordpress-mobile/release-toolkit
Should `fastlane` be public dependency?
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 31
- Forks
- 10
- Avg merge
- 5h 45m
- Merged PRs (30d)
- 2
Description
Currently, fastlane is a development dependency to this gem:
I haven't verified whether there's a rationale behind it or if it's the default behavior when Fastlane creates a plugin, but I think it would be more appropriate to make it a public dependency.
I run into this in setting up a new project. I though it would have been enough to add the plugin to get access to Fastlane, but that wasn't the case. I found that inconvenient, because I now had to specify two gems instead of one.
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
Start with fastlane-plugin-wpmreleasetoolkit.gemspec at the dependency declaration around line 54. Check how fastlane is currently declared and how the gem is packaged, then verify the dependency behavior during gem installation. Done means the dependency classification matches the intended plugin setup and the existing packaging checks remain valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100