However, users opening a workspace for a project still benefit consume and benefit from prebuilds, regardless if they don't have access through an org.
Although this may sound ok, it creates less value of having access to the project or the org that owns and configured prebuilds.
Proposal
Stop consuming prebuilds when you have no access to the project.
Future iterations could inlude:
Nudging users about the benefit of prebuilds
Nudging users to request access to orgs in order to benefit from prebuilds.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Problem to solve
Prebuilds now require a project to be enabled, see https://github.com/gitpod-io/gitpod/issues/9898 and https://github.com/gitpod-io/gitpod/pull/15026.
However, users opening a workspace for a project still benefit consume and benefit from prebuilds, regardless if they don't have access through an org.
Although this may sound ok, it creates less value of having access to the project or the org that owns and configured prebuilds.
Proposal
Stop consuming prebuilds when you have no access to the project.
Future iterations could inlude: