Skip to content

Handle missing project configuration when the person who added a project left a team or a repository #7220

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
gtsiolis opened this issue Dec 13, 2021 · 2 comments
Labels
component: dashboard feature: teams and projects [DEPRECATED] Please, use feature: organizations or feature: projects labels instead. meta: never-stale This issue can never become stale team: webapp Issue belongs to the WebApp team type: improvement Improves an existing feature or existing code user experience

Comments

@gtsiolis
Copy link
Contributor

Problem to solve

Currently, when the team member who added a project leaves a team or repository at GitLab:

  1. We don't have a way reconfigure the project using a new token from another team member ❗
  2. Users are still allowed to trigger prebuilds even if the webhook has been removed ❗

Could not reproduce the above for GitHub repositories as we'll need to set up the GitHub App.

Proposal

Following #7010, let's introduce a way to also reconfigure a project and re-installing a new webhook, etc.

This could be done using a new project settings area.

TBD (To be discussed)

@gtsiolis gtsiolis added user experience component: dashboard type: improvement Improves an existing feature or existing code feature: teams and projects [DEPRECATED] Please, use feature: organizations or feature: projects labels instead. team: webapp Issue belongs to the WebApp team labels Dec 13, 2021
@jldec
Copy link
Contributor

jldec commented Jan 1, 2022

Thanks @gtsiolis
Could you please provide more details
(a) how to reproduce this issue (Is this specific to GitLab?)
(b) what is the unwanted outcome experienced by other Gitpod users?

@stale
Copy link

stale bot commented Apr 2, 2022

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.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Apr 2, 2022
@gtsiolis gtsiolis added the meta: never-stale This issue can never become stale label Apr 2, 2022
@stale stale bot removed the meta: stale This issue/PR is stale and will be closed soon label Apr 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: dashboard feature: teams and projects [DEPRECATED] Please, use feature: organizations or feature: projects labels instead. meta: never-stale This issue can never become stale team: webapp Issue belongs to the WebApp team type: improvement Improves an existing feature or existing code user experience
Projects
None yet
Development

No branches or pull requests

2 participants