Inform users that enabling prebuilds (adding a project) requires proper permissions in the project addition flow

[gtsiolis]

Problem to solve

Adding a project and enabling prebuilds requires proper permissions (see https://github.com/gitpod-io/gitpod/issues/16849).

However, this is not quite visible for users.

Adding a project is also documented as an available feature for all org members, see relevant docs.

See also relevant discussion (internal):

Also, given the existing behavior and confusion around it, it's clear the UX is buggy, as the question isn't answered when using the New Project wizard.

Proposal

Inform users that enabling prebuilds (adding a project) requires proper permissions in the project addition flow.

Possibly adding a footnote could help.

[stale[bot]]

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.

[loujaybee]

What do you mean by "requires proper permissions" in this context, @gtsiolis ?

[gtsiolis]

@loujaybee Re-posting from the issue description in https://github.com/gitpod-io/gitpod/issues/16849 (closed in favor of EXP-344):

... enabling prebuilds requires:

• Maintainer user role for GitLab, see relevant docs.
• Admin user role for GitHub, see relevant docs.
• Administrator role for Bitbucket, see relevant docs.

[github-actions[bot]]

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.