Fastlane: When I run "fastlane" without any parameter, I receive all available lanes, including the private lanes.

[sebastianvarela]

fastlane 1.89.0

Hi! The first thing i wanna say is: This tools is amazing :)
After that, i explain my situation:

• I have one Fastfile with a Generic File that contains some private lanes
• When I run "fastlane" without any parameter, I receive all available lanes, including the private lanes.
• If I select one lane marked as private, i receive an error:

[01:00:23]: Welcome to fastlane! Here's what your app is setup to do:
+--------+--------------------------+------------------------------+
|                      Available lanes to run                      |
+--------+--------------------------+------------------------------+
| Number | Lane Name                | Description                  |
+--------+--------------------------+------------------------------+
| 1      | ios prepare_to_build     |                              |
| 2      | ios launch_build         |                              |
| 3      | ios generate_all_builds  |                              |
| 4      | ios run_job              |                              |
| 5      | ios check_build          |                              |
| 6      | ios resolve_dependencies |                              |
| 7      | ios do_snapshot          |                              |
| 8      | ios do_release           |                              |
| 0      | cancel                   | No selection, exit fastlane! |
+--------+--------------------------+------------------------------+
Which number would you like run?
4
[01:00:25]: Running lane `ios run_job`. Next time you can do this by directly typing `fastlane ios run_job` 🚀.
[01:00:26]: Variable Dump:
[01:00:26]: {:DEFAULT_PLATFORM=>:ios}
[01:00:26]: You can't call the private lane 'run_job' directly

Is this an error or is intentional? For what reason all private lanes are listed if I can not run directly?

Thank you!

[KrauseFx]

Hey @sebastianvarela, thanks for the report, that's not by design, and definitely something we should fix! Thanks for the precise description of the issue 👍

[asfalcone]

Submitted a PR for this 👍

[sebastianvarela]

@asfalcone, @KrauseFx Thank you! :)